SAP System Administration Made Easy007

Chapter 17: Change Management
Transporting Objects
3. Enter the transport command.

< To specify an individual transport, enter:
tp import <transport> <target sid> client=<target client>
tp import devk900023 prd client=100
Where the:
Transport number is devk900023
Target system is PRD
Target client number is 100
< To import the entire import buffer, enter:
tp import all <target sid>
tp import all prd
You may be instructed in an SAP note or by the SAPNet hotline to use Unconditional codes
or U codes. These are special program option switches that the tp program uses during the
import process.
< In NT, use QuickSlice, an application included with the NT resource kit, and the CPU
activity in the NT Performance Monitor to monitor the import process. After a few
times, you will recognize the activity pattern of a transport.
< In UNIX, use the utilities top or xload to monitor the import process.
1. Record the start and finish time for the transport on the transport log or the transport
form.
2. Check the exit code.
If you receive an exit code of 8 or higher, the import failed. You must resolve the
problem and reimport the transport. If you get a return code of 8, there is a known
condition where this return code does not match the transport log. This condition is
described in Checking the Transport Log section below.
3. Check the transport log (see below).
&KHFNLQJWKH7UDQVSRUW/RJ7UDQVDFWLRQ6(
:K\
The transport log indicates why a transport failed.
+RZ
The information in this chapter is only a portion of the first half of the process, that is,
determining if the transport succeeded or failed. The second half of the process,
investigating why the transport failed, is not covered. If the transport involves an object
such as an ABAP program or SAPscript layout, you will need the assistance of your
programmers to determine why it failed and how to fix it.
System Administration Made Easy

17–35
After the transport is completed, check the transport’s exit code:

< 0 = OK
< 4 = Warning
< 8 = Error
< 12 = Severe Error
If you receive an exit code of 8 or higher, the import failed. You must resolve the problem
and re-import the transport.
The transport could still have failed even if you did not receive a failed return code. The
final test is to verify in the target system that the transport arrived properly. The developer
and functional area owner are responsible for this verification.
&KHFNLQJWKH7UDQVSRUW/RJ
*XLGHG7RXU

1RWHYou must check the transport log from the transaction that released the transport (SE09 or SE10).
1. In the Command field, enter transaction SE10 and choose Enter

(or from the SAP standard menu, choose Tools → Accelerated SAP → Customizing →
SE10-Customizing Organizer).
2. Under Category, select:
< Customizing
< Workbench
< All clients
3. Under Request status:
< Deselect Modifiable.
2
< Select Released.
4. Enter a date range in the Last changed
From and To fields to limit the 3 4
amount of requests to review.
5. Choose Display.
5
Release 4.6A/B
17–36
6. Select the request.

7. Choose .
8. On the Import line, check the return

message and code:
< 0 – Successful
< 4 – Warnings occurred
< 8 – Performed with errors
< 12+ – Transport was terminated
8
A return code of 8 or higher is a

failed transport.
9. If you see a warning in step 8,
choose display log for the line with
the warning.

17–37
10. Choose to drill down for

additional details.
11. The status bar indicates how many
levels you have drilled down.
10
11
You may run into a rare inconsistency between the return code in this log and the return code
when you ran the import program tp. This condition occurs when the tp program ends with a
return code 8 (Error) and the log above shows a maximum return code of 4 (Warning). This
inconsistency is caused by a step in the import that is not associated with the transport number
(in the example RW6K9000079). Thus when the log is reviewed, the maximum return code of 4
[(and not 8) (Warning)] appears. However, it is still a failed transport.
The TMS method does not have this inconsistency.
Release 4.6A/B
17–38
&KDSWHU 7URXEOHVKRRWLQJ
&RQWHQWV
Overview ................................................................................................................18–2
Basic Troubleshooting Techniques ....................................................................18–2
System Administration Made Easy 18–1

Chapter 18: Troubleshooting
Overview
2YHUYLHZ
This chapter is a basic problem solving chapter. We will present you with some of the tools
and techniques to help you solve the problem yourself. We will not be going into advanced
troubleshooting techniques. Troubleshooting is learned by doing; the more experience you
have, the better you become.
The next chapter is on performance tuning. Performance tuning is a specialized
troubleshooting, so troubleshooting techniques are also relevant for performance tuning.
%DVLF7URXEOHVKRRWLQJ7HFKQLTXHV
The general procedure when working on troubleshooting is not new. It is the standard
problem solving procedure that has been in use for years by many professions. Your auto
mechanic would follow the same procedure when repairing your car:
< Gather data
< Analyze the problem
< Evaluate the alternatives
< Make a change
Remember to make only one change at a time.
< Document the changes
< Evaluate the results
*DWKHU'DWD
< Ask the following questions:
What is the problem?
What error messages, dumps, or other diagnostic aids are available from the
problem?
What conditions caused the problem?
Is the problem repeatable?
< To analyze the problem, use your available tools, such as:
System Log (SM21)
Update Failure (SM13)
ABAP Dump (SM22)
Spool (SP01)
Release 4.6A/B
18–2
Basic Troubleshooting Techniques
$QDO\]HWKH3UREOHP
< What are the resources you have to help solve the problem:
Online documentation
Reference books
SAP notes
Other customers (this is your network)
< Call for assistance:
Consultants
SAPNet help desk
(YDOXDWHWKH$OWHUQDWLYHV
0DNHRQO\2QH&KDQJHDWD7LPH
< If there is a problem, and you made several changes at once, you will not know which
change caused or fixed a problem.
< There are times where several changes need to be made, to fix a problem.
Unless they must be done together, such as related program changes, make the changes
separately.
'RFXPHQWWKH&KDQJHV
< If a change causes a problem, you need to undo the change.
To do that you need to know what the configuration was before the change and what
you did.
< If the change needs to be applied to multiple systems, you need to know exactly what
changes to make and how to do it. This process must be repeated exactly the same on all
systems.

18–3
*HWWKH&RPSOHWH(UURU0HVVDJH
*XLGHG7RXU

When you get an error message in an R/3 transaction, you need all the information on the error to forward
to SAP. To get the complete error message, do the following:
1. When an error occurs, the field
with the error is highlighted.
2. Double-click on the error message.
3. The error message appears in the

dialog box.
4. Record the relevant information
from the screen to send to SAP. 3
Release 4.6A/B
18–4
*HWWKH6$33DWFK/HYHO
:KDW
This level is the R/3 kernel patch level that is being used.
:K\
This patch level is needed when submitting problem messages to SAP. It tells the hot line
personnel on what kernel patch level you are. Different problems are fixed in different patch
levels.

([DPSOH
You are on patch level 50 and have a particular problem. The fix to your problem may
have been done in patch level 61. This level identifies that the problem is an older kernel
that contains the problem. The solution is to upgrade to the current kernel, “at least” patch
level 61.
+RZ
*XLGHG7RXU

1. In the Command field, enter transaction SM51 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → System monitoring →
SM51-Servers).
2. Select the central instance (for
example, pa100767_SAS_00).
3. Choose Release notes.
3

18–5
4. Record the Patch level (for our

example, we chose Patch level 55).
'HWHUPLQLQJ:KDW6XSSRUW3DFNDJHV+DYH%HHQ$SSOLHG
:KDW
A support package is an SAP-provided R/3 fix and is similar to an NT Service Pack.
:K\
As with the SAP Patch level, problems you have may be related to the level of the applied
support package.
Release 4.6A/B
18–6
+RZ
*XLGHG7RXU

1. From the menu bar, choose System → Status.

2. Choose .
3. Choose the Patches tab.

3

18–7
4. In this example, the following

patches have been applied:
< SPAM update 17-Sept-99
< Support Package 01 for 4.6A
Patch Status values are:
< N – The patch has not yet been
applied
< I – Patch has been successfully
applied
< ? – Patch application has been
aborted
The name of a Support Package is interpreted as follows:

< SAPKH<release><sequence_number>
< SAPKH46A01 is interpreted as SAPKH / 46A / 01, and is for Release 4.6A and is the first Support
Package.
Release 4.6A/B
18–8
&KDSWHU 3HUIRUPDQFH
&RQWHQWV
Overview ................................................................................................................19–2
General Procedure ................................................................................................19–3
R/3...........................................................................................................................19–4
Database ..............................................................................................................19–11
Operating System ...............................................................................................19–11
Hardware..............................................................................................................19–15

Chapter 19: Performance
Overview
2YHUYLHZ
This chapter is an introduction to performance issues in R/3. We provide only general

guidelines, not detailed performance tuning instructions. It is not possible in one chapter, to
provide the breadth and depth of information available in the SAP training class or the
Performance Optimization book. For more detailed performance tuning, we recommend the
following resources:
< BC315 – R/3 Workload Analysis (the SAP Performance Tuning class)
< SAP R/3 Performance Optimization, by Thomas Schneider, SAP’s TCC organization, which
recently published a book on performance optimization.
Performance tuning is specialized troubleshooting. Since you are trying to solve
performance issues, all troubleshooting techniques are also relevant.
Rather than using database and operating system-specific details, where possible, we will be
using R/3 transactions to access relevant database and operating system data. This
approach makes the information database and operating system independent.
&ULWLFDO$VVXPSWLRQ
The hardware, operating system, database, and R/3 have been properly installed based
upon SAP’s recommendations.
:K\
As with the design of this book, performance tuning has to have a starting point. This point
is the SAP-recommended configuration for hardware, database, operating system, network,
etc.
An extreme example (that did occur with a customer) is where the operating system, the
database, and R/3 has been installed on a single logical drive. In this situation, all the drives
in the server were configured in a single RAID5 array and treated as a single, huge drive.
This situation created a classic condition known as “head contention,” where R/3, the
database, and the operating system all simultaneously competing for the same disk drive
head.
Head contention is similar to you being asked to do many things at the same time, such as:
< Cook dinner
< Read a book
< Help your child with homework
< Water the yard
< Fix the fence
You run around doing a little of each task then going to the next. None of the tasks get done
with any reasonable speed.
Release 4.6A/B
19–2
General Procedure
This is an example of a problem that is not new. Head contention existed in the early days of
computing. The solution now is essentially the same as it was back then, that is, to spread
the data over multiple drives.
3ULRULW\RI(YDOXDWLRQ
The SAP EarlyWatch group has determined that the majority of the performance issues and
gains are from within R/3. This gain is followed first by database issues, then operating
system, then hardware. Thus we will primarily discuss R/3 performance issues.
*HQHUDO3URFHGXUH
The general procedure when working on performance issues is not new. It is the standard
problem-solving procedure:
< Gather data
< Analyze the problem
< Evaluate the alternatives
< Make only one change at a time
If there is a problem, you will not know which change caused a problem. There are
times where several changes need to be made to fix a problem. Even so, unless they
must be done together, such as related program changes, make the changes one at a
time.
< Document the changes.
If a change causes a problem, you need to undo the change.
To do that you need to know what the configuration was before the change and
what you did.
If the change needs to be applied to multiple systems, you need to know exactly
what changes to make, and how to do it.
This process must be repeated exactly the same on all systems.

19–3
R/3
5
One of the most common reasons for R/3 performance problems is poorly written custom
(or modified standard) ABAP programs.
:RUNORDG$QDO\VLVRIWKH6\VWHP7UDQVDFWLRQ67
:KDW
Workload analysis is used to determine system performance.
+RZ
You should check statistics and record trends to get a “feel” for the system’s behavior and
performance. Understanding the system when it is running well helps you determine what
changes may need to be made when it is running poorly.
*XLGHG7RXU

1. In the Command field, enter transaction ST03 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → Performance → Workload →
ST03-Analysis).
2. Choose Data base server or This
application server.
(In this example, we chose This
application server,
pal101003_SAS_00.)
Release 4.6A/B
19–4
R/3
3. Select a time period to analyze.

(In this example, we chose Last
minute load.)
4. Enter how many minutes back to

analyze, or choose Other selection
to specify a date and time period
to analyze.
In this example, we chose Other
selection.
4
5. Under Time interval to be analyzed

is, enter the Date and time range to
6
be analyzed.
6. Choose .

19–5
R/3
7. Check the Current value under

Task types (for example, Total).
The task types are:
< Total
10
< Dialog
< Background
< RFC
8. Choose the appropriate button to
view performance values for that
Task type.
9. Examine Av. response time.
If this value is less than 1,000 ms (1
second), the response time meets
the target standard response time. 9
For more information on Av.

response time, see notes below.
10. Choose Transaction profile.
8
7
Judgment must be applied when reviewing statistical values. If you just started the R/3
System, the buffers will be empty and many of the statistics will be unfavorable. Once the
buffers are loaded, values can be properly evaluated.
In this example, the Av. response time of almost 4 seconds must be evaluated with other
factors in mind.
The R/3 user default for a decimal point is a comma. If your default profile for decimal point,
(point or comma) is not appropriately set, the display may be misread. For example, rather
than 3,888 ms, it would read 3.888 ms. Quite a difference!
Release 4.6A/B
19–6
R/3
11. Click on any cell in the Response

time avg column.
12. Choose .
12
11
Analysis of transaction ST03 is covered in BC315 (the Workload Analysis and Tuning class).
We recommend you take this class.
13. The programs and transactions are

now sorted in average response
time order.
13

19–7
R/3
A few standard functional transactions will exceed the one-second guideline. They include,
but are not limited to the following:
Type Transaction
Create Sales Order VA01

Change Sales Order VA02
Display Sales Order VA03
Create Billing Document VF01
Create Delivery VL01
Maintain Master HR data PA30
%XIIHUV67
:KDW
The buffer tune summary transaction displays the R/3 buffer performance statistics. It is
used to tune buffer parameters of R/3 and, to a lesser degree, the R/3 database and
operating system.
:K\
The buffer is important because significant buffer swapping reduces performance. Look
under Swaps for red entries. Regularly check these entries to establish trends and get a feel
for buffer behavior.
Release 4.6A/B
19–8
R/3
*XLGHG7RXU

1. In the Command field, enter transaction ST02 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → Performance
→ Setup/Buffers → ST02-Buffers).
2a 2b
2. The two important things to review on the above screen are:

a. Hit Ratio
The target value is 95 percent and higher. Soon after starting the system, this value is
typically low, because buffers are empty. The hit ratio will increase as the system is
used and the buffers are loaded. It usually takes a day to load the buffers that are
normally used.
b. Swaps
The target value is less than 1,000. Swaps occur when the necessary data is not in the
buffer. The system has to retrieve the data from the database. The swap value is reset
to zero (0) when the system is restarted.

19–9
R/3
Analysis of transaction ST02 is covered in BC315 (the Workload Analysis and Tuning
class). We recommend you take this class.
0HPRU\'HIUDJPHQWDWLRQ
:KDW
A computer’s memory behaves similar to a hard disk. As different programs execute, they
are loaded into, and later deleted out of, memory. Over time, like a hard disk, the usage of
the computer’s memory becomes fragmented with unused spaces scattered throughout.
:K\
At a certain point you may have sufficient “free memory” (that is, the total of all the unused
spaces), but not a contiguous (single) piece of memory large enough to allow certain
programs to execute. At that point, those types of programs attempting to run that need
contiguous memory will fail because they cannot be loaded into memory.
+RZ
To defragment the system’s memory:

1. Stop R/3.
This step requires stopping R/3 on all application and database servers. (For more
information, see Start/Stop R/3 in chapter 10.)
2. Restart R/3.
You only need to restart R/3, you do not need to cycle the server.
When R/3 is restarted, the buffers are refreshed. This process means that the first person
who accesses the buffered object will have a long response because the system must get the
data from disk and load it into the buffer. The second person will have a normal (quick)
response time. This process repeats until all normally used objects are loaded into the
buffer, which usually takes up to a day to accomplish.
Release 4.6A/B
19–10
Database
'DWDEDVH
See chapter 13 (Database Administration – Microsoft SQL Server) for the database-related
performance tuning transactions:
< Activity - ST04
< Tables/Indexes - DB02
2SHUDWLQJ6\VWHP
2SHUDWLQJ6\VWHP0RQLWRU26
:KDW
The operating system monitor allows you to view relevant operating system and hardware
details.
The operating system-related detail, such as:
< Memory paging
< Operating system log
In addition, the following hardware details are available:
< CPU utilization
< Free space on disks
:K\
Certain operating system items will impact R/3 performance.

19–11
Operating System
+RZ
*XLGHG7RXU

1. In the Command field, enter transaction OS07 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → Performance →
Operating System → Remote → OS07-Activity).
2. Select the appropriate server.
3. Choose .
3
This screen is a snapshot of the CPU,

Memory, Swap, and Disk response data.
4. To analyze, choose Detail analysis
menu.
4
Release 4.6A/B
19–12
Operating System
5. Choose an item under Previous hours

(for example, Memory or OS Log).
This screen shows CPU utilization

over time.

19–13
Operating System
This window shows the memory

paging and free memory over time.
This is the Operating System Log.
Release 4.6A/B
19–14
Hardware
+DUGZDUH
&38DQG'LVN
Also see Operating System – Operating System Monitor (OS07) to get data on:
< CPU utilization
< Free space on disks
0HPRU\
The hardware item that has the largest effect on R/3 performance is memory. The R/3
System uses memory extensively. By keeping data in buffer, physical access to the drives is
reduced. Thus, in general, the more memory you have, the faster R/3 will run.
Physical access to the drives is the slowest activity.

19–15
Hardware
Release 4.6A/B
19–16
&KDSWHU 6$31HW³:HE)URQWHQG
&RQWHQWV
Overview ................................................................................................................20–2
Logging on to SAPNet ..........................................................................................20–3
Online Services .....................................................................................................20–4
Solving a Problem with SAPNet ..........................................................................20–5
Registering a Developer or Object ....................................................................20–15
Online Correction Support.................................................................................20–24

Chapter 20: SAPNet—Web Frontend
Overview
2YHUYLHZ
SAPNet–Web Frontend (SAPNet–web) is the internet access to SAP resources and SAPNet–
R/3 (formerly OSS) functions such as:
< Registering developers and objects
< Searching for SAP notes
< Downloading support packages
Most of the OSS functions will be migrated to SAPNet. The entering and retrieving of
customer messages on SAPNet has just become available and is currently in pilot.
However, not all OSS functions will be migrated to SAPNet. The opening and use of the
SAP service connections for Earlywatch and SAP hotline access to customer systems will
remain in OSS or SAPNet–R/3.
We recommend that you use SAPNet–Web as your primary SAPNet access method. For
most companies with an existing (flat fee) internet access line, the cost of the internet
access is already paid for. The SAP service connection required for SAPNet-R/3, if using
ISDN, is additional per minute cost.
+RZ
The prerequisites to use SAPNet–Web are:

< An internet connection
< A browser
SAPNet works better with Microsoft Internet Explorer.
< A valid SAPNet/OSS user ID and password
Release 4.6A/B
20–2
Logging on to SAPNet
/RJJLQJRQWR6$31HW
*XLGHG7RXU

1. In your web browser, enter www.sapnet.sap.com.

2. In User Name, enter your OSS/SAPNet user ID.
3. In Password, enter your OSS/SAPNet password.
2
3
This main screen (SAPNet for Customers and

Partners) is the starting screen for the following
tasks.

20–3
Online Services
2QOLQH6HUYLFHV
*XLGHG7RXU

1. In the left frame, scroll down to Services.

2. Choose Online Services.
The Online Services main screen appears.

Most of the SAPNet functions used by systems
administrators are grouped in this screen.
Release 4.6A/B
20–4
Solving a Problem with SAPNet
6ROYLQJD3UREOHPZLWK6$31HW
If you have a particular problem or question, you should search:

< The online documentation
< SAP notes.
This large database contains problem notes.
6HDUFKLQJIRU6$31RWHV
*XLGHG7RXU

SAP Notes were formerly known as OSS Notes.

1. On the Online Services screen, choose SAP Notes.
2. SAP Notes are divided into several topics. For

example, you can retrieve a list of notes on the:
< Installation and upgrade processes
< Managing Y2K issues
< Latest or “hot” news about R/3

20–5
3. The search can be done in one of many different

ways:
a. You can use a text search with the following
options:
< AND – the note must contain all of the
words in the search text field
< OR – the note must contain at least one
3a
of the words in the search text field
< PHRASE – the note must contain the 3b
words in the exact order specified in the
field.
b. You can also specify the specific:
< Note Number
< R/3 Release
< Application Area
< Database
You cannot simultaneously specify a Note
Number and Search Text.
4. On the SAP Notes Search screen, in each of the

following fields, enter the following text:
a. In Search Text, enter spool system
b. In Search Mode, select all given words (AND)
c. In Release, enter 46A
d. In Database, enter a database name
4a
5. Choose Submit. 4b
4c
4d
5
Release 4.6A/B
20–6
6. The results from the criteria are displayed. Each

page contains 20 hits and the total number of
hits is limited to 500.
7. Choose the first note.
6
7
8. Review the note.

9. Close this window and return to the SAP Notes
list.
7R6HDUFKIRU1RWHV5HODWHGWR,QVWDOODWLRQ
1. On the left frame, click the node (+) next to

Installation folder.
The folder contents appear in the main frame.
2. Choose a note.
2
1

20–7
3. The note gives additional

information on the 4.5B R/3
installation in the NT/Oracle
environment.
4. Return to the Online Services main
menu.
3
&XVWRPHU0HVVDJHV
1RWH As this guidebook is going to print, the Customer Message function has just been
released to SAPNet-Web. Since this function is in pilot mode, it may change from the
process described here. At present, you can only create and view messages via SAPNet-
Web, modifying messages is only possible via SAPNet-R/3.
If you have searched both the online documentation and SAP notes and not found the
answer to your question or problem, then you should submit a SAPNet message for
assistance.
1RWH The SAPNet customer message function is not meant to replace consulting.
Messages entered into SAPNet are for reporting and getting resolution on SAP problems
or bugs. If a message is interpreted as a request for consulting information, it will be
returned to you, and you will be advised to seek consulting assistance.
Release 4.6A/B
20–8
(QWHULQJ&XVWRPHU0HVVDJHV
Include as much information as possible in your message, so the SAPNet Hotline
consultants can help you. Indicate where in the online documentation you have searched
and which SAP notes you have reviewed.
3ULRULW\WDEOH
Assign your message a priority from the following table below:
Priority Situation
Very High < In your production system, only for system or application
shutdown
< In your nonproductive system, during a critical project phase
These messages are reviewed by an Online Service System/SAPNet
consultant within 30 minutes of arrival. If the problem does not fall
within the defined description for a “very high” priority problem,
the priority is immediately reduced.
Do not assign a message this priority if you cannot be available to
receive a call back from SAP. If SAP attempts to call you and you
cannot be reached, your message may be downgraded.
High When important applications or subprograms fail in function, or for

a system shutdown in a nonproductive system.
Medium For errors with less serious consequences than the above two cases,
where the operation of the productive system is not seriously
affected.
Low For minor errors, such as documentation errors, typographical

mistakes, etc.
Use care when assigning a priority to your message. If the problem does not meet the Very
High criteria, assigning the message this priority will not guarantee you a quicker response
time.

20–9
The following list contains hints that can improve total problem resolution time:
&RPSRQHQW
< If you know the specific component, assign it.
If you do not know it, do not assign to a detailed component level (for example, assign it
to level 3, BC-CCM-PRN rather than a level 4, BC-CCM-PRN-DVM). The Online Service
System Hotline consultant can assign a specific component. If you assign the message to
a wrong component, and it is forwarded to the incorrect person, time is lost. It will take
that much more time to resolve your problem.
< Be aware that the cause of the problem may be in an area other than the module you are
working on.
3UREOHP'HVFULSWLRQ
< Be clear and descriptive.
The better the information you provide, the better the results. Information that is clear to
you may not be clear to the hotline consultant.
< Provide enough data so that SAPNet Hotline personnel will not have to ask additional
questions before beginning work on your problem.
Examples of complete data includes:
If there is an error message, enter it exactly as it appears.
Provide the transaction or menu path describing where the error or problem
occurred.
Indicate if the problem can be duplicated on your test system.
Describe the circumstances that created the problem.
Describe anything unique about the data entered in the transaction where the
problem occurred.
List which problem-related SAP notes that have been reviewed and which notes
have been applied.
List which actions and research you have already performed.
< The following examples are messages in which the SAPNet hotline requires more
information before beginning on the problem:
“FB01 does not work.”
“The system is slow.”
Keep your system technical information in SAPNet current and correct. This information
is used by hotline personnel when they work on your problem.
Release 4.6A/B
20–10
+RZ
*XLGHG7RXU

(QWHULQJ&XVWRPHU0HVVDJHV
1. On the Online Services screen, choose

Customer Messages.
2. Note that the Customer messages

function is in pilot.
The final process many change from
the steps in this guidebook.
3. Choose Message Wizard.
3
3

20–11
4. Under Reporter, check that the values

in the fields are correct.
If it is not, you must use SAPNet-
R/3 to correct your user
information.
5. In System type, select the type of your
system:
< Development 4
< Production
< Test
6. In Installation, choose the installation
that your message is for.
7. In Release, choose the R/3 release of 5
your system from display options. 6
8. In Add-on, choose the add-on that 7
you are running. 8
9
9. In Add-on release, choose the release 10
of the add-on.
10. Choose continue.
11. In Oper system (operating system),

click the down arrow and choose
your operating system.
12. In Database, click the down arrow
and choose your database.
13. In Frontend, click the down arrow
and choose your frontend.
14. Choose continue.
11
12
13
14
Release 4.6A/B
20–12
15. Under Classification, in Priority click

the down arrow and choose the
appropriate priority for your
message.
Use the table on page 20–9 to
determine the proper priority level.
16. In Components, entering the fields in
order (from 1 to 3), click the down
arrow and choose the component for
the message.
17. Choose continue. 15
16
17
18. In Language, click the down arrow

and choose the language for the
message.
19. In Short text, enter a short (one line)
problem description.
20. In Long text, enter a complete
description of the problem.
21. Choose Send to SAP.
18
19
20 21
9LHZLQJ&XVWRPHU0HVVDJHV
The response to your message is often in the form of an electronic message, rather than a
telephone call. It is, therefore, important to monitor the status of your messages.

20–13
9LHZLQJ&XVWRPHU0HVVDJHV
1. On the SAPNet screen, on the menu
bar, choose Inbox.
2. Choose Sent SAPNet Items.
3. Messages will be in the following

three categories:
< Messages – to be sent to SAP
< Messages – in process at SAP
< Messages – solution proposed by
SAP
Release 4.6A/B
20–14
Registering a Developer or Object
5HJLVWHULQJD'HYHORSHURU2EMHFW
:KDW
To modify an SAP object, both the developer and the object that will be modified need to be
registered with SAP. A developer, once registered for the installation, does not have to
register again. Similarly, an SAP object once registered for the installation, does not have to
be registered again. It is for this reason that on the registration screen either or both the
developer or object access key would be required.
:K\
< Only an SAP-registered developer can make changes to SAP objects.
Restricting access to registered developers provides a record of who has made changes
to the system.
< Registering an SAP object provides a record of which SAP objects have been modified
by the customer.
The assumption is that if you requested an object access key, you will be modifying the
object.
+RZ
See the following sections for registering a developer and an SAP object.
5HJLVWHULQJD'HYHORSHU
To modify an SAP object, the developer needs to be registered with SAP. Once registered for
the installation, the developer does not have to register again.
:K\
Only an SAP-registered developer can make changes to SAP objects. Restricting access to
registered developers provides a record of who has made changes to the system.
+RZ
In the following procedure:

1. The developer requests a developer key
2. The system administrator obtains the key
3. The developer enters the key

20–15
*XLGHG7RXU

'HYHORSHU5HTXHVWV'HYHORSHU.H\
1. This screen is seen by the
developer when a developer key is
required.
a. If the developer Access key is
blank, you need to obtain a
developer access key. b
b. Give the developer User name a
(2) to the system administrator
to get a developer access key.
7KH6\VWHP$GPLQLVWUDWRU*HWVWKH$FFHVV.H\
1. On the Online Services screen, choose SSCR.
Release 4.6A/B
20–16
2. On the SSCR screen, you can register and get

keys for:
< Developers
< SAP objects that will be changed
3. Choose Start SSCR now.
5HJLVWHULQJD'HYHORSHU
1. If your site has several R/3 installations, select
the one for which you wish to perform
registrations.
2. Choose Register Developer.
3. In Developer, enter the developer’s user ID.

4. Choose Register.

20–17
5. The registration information for the developer is

displayed.
If the registration date is not today’s date and
the registration name is not the name of the user
who just submitted the request to register a
developer, the developer has been previously
registered.
6. Record the Registration key.
The generated key enables the user to create or
change customer objects and change SAP
6
objects. The registration is done only once for
each developer.
(QWHUWKH'HYHORSHU.H\
In the development system:
1. In the developer Access key field,
the developer enters the key
received from the system
administrator.
Release 4.6A/B
20–18
'HOHWLQJD'HYHORSHU
On the same screen that was used to
register a developer:
1. In Developer, enter the user ID of the
developer to delete.
2. Select Delete.
3. Choose Register.
4. To check if the deletion is
successful, choose Overview, which 4
displays a list of developers.
5HJLVWHULQJDQ2EMHFW
:K\
Registering an SAP object provides a record of which SAP objects have been modified by
the customer. The assumption is that if you requested an object access key, you will be
modifying the object. If the customer modifies an object and problems arise, resolving the
problem may be the customer’s responsibility. If an object is not modified and problems
arise, resolving the problem is SAP’s responsibility.
+RZ
In the following procedure:

1. The developer requests a developer key
2. The system administrator obtains the key
3. The developer enters the key

20–19
*XLGHG7RXU

'HYHORSHU5HTXHVWV2EMHFW.H\
1. This screen is seen by the
developer when an object key is
required:
a. If the object Access key is blank,
you need to obtain an object
access key.
b. Give the three object fields to
the system administrator (for
example, R3TR, PROG, b
RSPARAM). c
All three fields are required to a
obtain the object key.
c. If you are in a mixed release
environment, also give the
system administrator the SAP
Release for the system.
7KH6\VWHP$GPLQLVWUDWRU*HWVWKH$FFHVV.H\
1. On the Online Services screen, choose SSCR.
Release 4.6A/B
20–20
2. On the SSCR screen, you can register and get

keys for:
< Developers
< SAP objects that will be changed
3. Choose Start SSCR now.
5HJLVWHULQJDQ2EMHFW
1. If your site has several R/3 installations, select

the one for which you wish to perform
registrations.
2. Choose Register Object.

20–21
3. TADIR is the table that contains R/3 repository

objects.
Information must be entered in the following
fields:
< Program ID
< Object
< Object name
In this example, we wish to change a program
(PROG) named RSPO0041. The entry is R3TR /
PROG / RSPO0041.
4. Select Advance correction to apply an SAP note, 4
and this note is an advance correction. 3
5. Choose Register.
6. Registration information for the object is

displayed.
If the registration date is not today’s date and
the registration name is not the name of the user
who logged onto SAPNet, the object has been
previously registered in this installation.
7. Record the Registration key.
Return to the Online Services main screen.
Release 4.6A/B
20–22
(QWHUWKH2EMHFW.H\
In the development system:
1. In Access key, the developer would enter the
object key received from the system
administrator.
10
'HOHWHDQ2EMHFW
From the Register Object Screen:
1. In TADIR Object, enter the Program
ID/Object/Object name of the object to
be deleted.
2. Select Delete.
3. Choose Register.
4. To check whether the deletion is
4
successful, choose Overview, which
displays a list of developers.
2
3

20–23
Online Correction Support
2QOLQH&RUUHFWLRQ6XSSRUW
The SAP Online Correction Support provides information and tools to retrieve support packages such as
hot packages, legal change packages, SPAM updates, etc.
*XLGHG7RXU

1. On the Online Services screen, choose Online

Correction Support.
2. In the left frame, choose Download.
Release 4.6A/B
20–24
*HWWLQJWKH/DWHVW63$0YHUVLRQ
Make sure that you have the latest version of the

SAP Patch Manager or SPAM on your R/3 System
before you apply any support packages:
1. To get the latest SPAM version, on the
download screen, choose SPAM Updates.
2. Choose SPAM Updates.
3. Choose the SPAM update for your release.

Use the date (for example, 17-Sept-1999) to
determine if the SPAM update is a newer
version than what you have.
The transport number for an R/3 release
(example SAPKD00029) does not change.

20–25
4. Choose Download.
5. Select Save this file to disk.

6. Choose OK.
7. Specify the directory where you want the

update to be saved.
8. Choose Save.
7
The downloading process begins.
9. Choose OK.
Release 4.6A/B
20–26
'RZQORDGLQJ6XSSRUW3DFNDJHV
1. On the download screen, from the left frame,
select R/3 Support Packages.
2. Select the appropriate release (for example,

select HP 4.6A on the left frame).
3. Select the appropriate support package.

The file size column tells you how large the
patch file is.
Make sure that your system has enough file

space to:
< Download the patch
< Upload the patch into usr/sap/trans/EPS/in
< Create the transport file in usr/sap/trans/da

20–27
4. From this screen, you have the following

options:
< Download the support package
< View the related SAP notes that apply to the
support package
< View the objects that are affected by the
support package
6SHFLILF6XSSRUW3DFNDJH5HODWHG1RWHV
To look at the notes related to the specific Support
Package:
1. On the Option screen, choose R/3 Notes.
Release 4.6A/B
20–28
The listed notes appear.

2. To display a note, click on it.
3. You can print the note or save it as any other

browser page.

20–29
'RZQORDGLQJ6XSSRU3DFNDJHV
To download the Support Package:
1. On the option screen, choose Download.
2. Select Save this file to disk.

3. Choose OK.
4. Specify the directory.

5. Choose Save.
Release 4.6A/B
20–30
The downloading process has begun.
6. After the download has completed, choose OK.
7
After downloading the support packages (whether SPAM update or support package), complete the
following steps:
1. Unpack the patch archive file (see Unpacking a CAR file in chapter 22).
2. Transfer the resulting *.ATT and *.PAT files to the /usr/sap/trans/EPS/in subdirectory.
Useful SAP Notes Description
83458 OCS Info: Downloading patches from SAPNet

97621 OCS Info: Online Correction Support (OCS)
169142 Online Correction Support (OCS)
36579 Questions and answers on the topic: SSCR
152170 Migration of support functions to SAPNet-Web frontend
169329 New functions in the SAPNet as of 09/05-06/99
86161 Registering developers and objects
69224 Access to the SAPNet server via OSS User ID

20–31
Release 4.6A/B
20–32
&KDSWHU 6$31HW²5)URQWHQG
&RQWHQWV
Overview ................................................................................................................21–2
Useful SAP Notes..................................................................................................21–3
Connecting to SAPNet–R/3 ..................................................................................21–3
Researching a Problem with SAPNet-R/3...........................................................21–6
Registering a Developer or Object ....................................................................21–22
Opening a Service Connection..........................................................................21–30

Chapter 21: SAPNet–R/3 Frontend
Overview
2YHUYLHZ
SAPNet–R/3 Frontend [SAPNet-R/3 (formerly OSS)] is a group of services offered by SAP

that is used to:
< Search for solutions to problems
< Enter problem messages
< Register developers and objects before changing SAP objects
< Open a service connection
This connection allows SAP personnel to log on to your system(s) when solving a
problem or performing an EarlyWatch session.
< Retrieve patches from SAP
Periodically, the SAPNet–R/3 user interface changes as the frontend is upgraded. Therefore,
screens may not appear as shown in this book or be the same over time.
In this chapter, you will learn how to:
< Connect to SAPNet–R/3
< Research problems about SAPNet–R/3
< Open a service connection
< Register a developer and an object
If you have an ISDN connection, the telephone bill can become high. ISDN is normally
billed “by the minute” of connect time. Manage the time that you are connected to
SAPNet-R/3, or you could get a large phone bill for your SAP service connection.
Check with your networking person or company about how your SAP service connection
is configured. Some will hold the ISDN connection open even if there is no traffic, which
could result in an even larger phone bill.
3UHUHTXLVLWHV
< The SAP Service connection must be set up and working
SAProuter must be installed and configured
OSS1 technical settings must be configured
< You must have a valid SAPNet/OSS user ID and password for your company
Release 4.6A/B
21–2
Useful SAP Notes
8VHIXO6$31RWHV
SAPNet R/3 – Note # Description
32789 OSS – Quick reference sheet

33221 Easy to Use guide for transaction OSS1 – SAPSERV4
&RQQHFWLQJWR6$31HW²5
*XLGHG7RXU

1. In the Command field, enter transaction OSS1 and choose Enter.

2. Choose Logon to the SAP Online
Service System.
Once you pass this screen, the SAP

service connection is open, and the
ISDN “billing meter” is running.
2
3. Select 1_PUBLIC.
4. Choose Continue.
3

21–3
Connecting to SAPNet–R/3
5. In User, enter your OSS/SAPNet

user ID.
8
6. In Password, enter your password.
7. In Language, enter your language
preference (for example, DE for
German). The default language is
English.
8. Choose .
5
6
This screen shows System News.

We recommend that you
periodically review these
headlines to see if any apply to
your system’s configuration.
9. Choose Continue.
Release 4.6A/B
21–4
Connecting to SAPNet–R/3
10. The Inbox is the main SAPNet–R/3

screen.
In the rest of this chapter, this
screen is repeatedly referenced as
the first screen of each process.

21–5
Researching a Problem with SAPNet-R/3
5HVHDUFKLQJD3UREOHPZLWK6$31HW5
SAPNet-R/3 contains a large database of problem notes. If you have a particular problem or
question, you should first search the online documentation, then search these notes. You can
also access SAP notes through SAPNet-Web.
)LQGLQJ1RWHVLQWKH6$31HW5
*XLGHG7RXU

1. On the main SAPNet–R/3 screen,

choose Gen. functions.
Release 4.6A/B
21–6
2. Choose Notes.
3. Choose Find.
4. Enter the search parameter(s) (for

example, sapserv4).
Additional search parameters
include: 4
a. Keywords with and/or logic 4a
b. Release number
c. Component 4a
d. Note number
4a
e. Priority
f. Category
5. Choose .
4b
4c
By using a combination of parameters,
you can search for: 4d
4e 4f
“High priority” notes
< Microsoft SQL Server
< R/3 Release 4.0B and higher 5

21–7
If the search is too broad, a warning message appears.
6. If the warning window appears,

you have two options: 6
< Option 1: To view all
matching entries, choose Yes.
< Option 2: To return to the
previous screen and refine the
search parameters or to
narrow the results, choose No.
In this example, we chose Yes
to list all 532 entries.
7. Select a note (for example, SAP

note 0016663).
8. Choose . 8
Release 4.6A/B
21–8
From this screen, you can read the

note online or download it to your 9
local PC. Once the note is
downloaded to your PC, print it
using a text editor or word
processor.
9. To download the note to your PC,

from the menu bar, choose
System → List → Save → Local file.
You can also download a note to

your PC by entering %pc in the
Command field.
10. Select unconverted.

11. Choose .
10
11
12. In File name, enter

<drive\path\filename>. 12
A suggested filename is the note
number and a short text
description. 13
13. Choose Transfer.

14. Once the file is downloaded to your local computer, you can view and print the file using a text editor
or a word processor.

21–9
(QWHULQJ&XVWRPHU0HVVDJHV3UREOHPVLQWR6$31HW5

If you have searched both the online documentation and SAP notes and not found the
answer to your question or problem, then submit a SAPNet message.
The SAPNet message function does not replace consulting. Messages entered into SAPNet
are for reporting and getting resolution on SAP problems or bugs. If a message is
interpreted as a request for consulting information, it will be returned to you, and you will
be advised to seek consulting assistance.
Include as much information as possible in your message, so the SAPNet Hotline

consultants will be able to best help you. Indicate where in the online documentation you
have searched and the individual SAP notes you have reviewed. Assign your message a
priority from the following table below:
Priority Situation
Very High < In your production system, only for system or application
shutdown
< In your nonproductive system, during a critical project phase
These messages are reviewed by an Online Service System/SAPNet
consultant within 30 minutes of arrival. If the problem does not fall
within the defined description for a “very high” priority problem,
the priority is immediately reduced.
Do not assign a message this priority if you cannot be available to
receive a call back from SAP. If SAP attempts to call you and you
cannot be reached, your message may be downgraded.
High This priority is for situations when important applications or

subprograms fail in function, or for a system shutdown in a
nonproductive system.
Medium This priority is for errors with less serious consequences than the
above two cases, where the operation of the productive system is
not seriously affected.
Low This priority is for minor errors, such as documentation errors,

typographical mistakes, etc.
Use care when assigning a priority to your message. If the problem does not meet the Very
High criteria, assigning the message this priority will not guarantee you a quicker response
time.
Release 4.6A/B
21–10
The following list contains hints that can improve total problem resolution time:
&RPSRQHQW
< If you know the specific component, assign it.
If you do not know it, do not assign to a detailed component level (for example, assign it
to level 3, BC-CCM-PRN rather than a level 4 BC-CCM-PRN-DVM). The SAPNet Hotline
consultant can assign a specific component. If you assign the message to a wrong
component, and it is forwarded to the incorrect person, time is lost. It will take that
much more time to resolve your problem.
< Be aware that the cause of the problem may be in an area other than the module you are
working on.
3UREOHPGHVFULSWLRQ
< Be clear and descriptive.
The better the information you provide, the better the results. Information that is clear to
you may not be clear to the hotline consultant.
< Provide enough data so that SAPNet Hotline personnel will not have to ask additional
questions before beginning work on your problem:
Examples of complete data includes:
If there is an error message, enter it exactly as it appears.
Provide the transaction or menu path describing where the error or problem
occurred.
Indicate if the problem can be duplicated on your test system.
Describe the circumstances that created the problem.
Describe anything unique about the data entered in the transaction where the
problem occurred.
List which problem-related SAP notes that have been reviewed and which notes
have been applied.
List which actions and research you have already performed.
< The following examples are messages in which the SAPNet hotline requires more
information before beginning on the problem:
“FB01 does not work.”
“The system is slow.”
Keep your system technical information in SAPNet current and correct. This information
is used by hotline personnel when they work on your problem.

21–11
*XLGHG7RXU


choose Messages.
2. Choose Create.
3. Select your system <SID> (for

example, SAS).
Depending on your installation,
this screen may not appear. 4
4. Choose .
Release 4.6A/B
21–12
From the message entry screen:

5. Verify phone and fax numbers. 15
6. Verify the R/3 release (required).
7. Verify the system type (required).
8. Enter the Component area where
the error occurred (required). 7
You can also choose to make a

6
selection.
9. Select the priority (see the table on
page 21–10 for a list of priorities.) 5
10. Enter a short description of the
9
problem (required).
8
11. Provide, where possible, the
following information: 10
< Kernel patch level
< Kernel release 11-14
< Transaction code or menu path
< Program name
< Error message
12. Describe the sequence of your
actions as precisely as possible.
13. Describe any modification(s) you
made to the standard system.
14. Provide the following remote
access information:
< System ID
< Client number
< User ID
< Type of connection
15. Choose Save.
To control access to your system and mange how long the service connection is open, request
that you be contacted to:
< Get the password
< Open the SAP service connection

21–13
16. Choose Yes.
16
17. The Status changes to Sent to SAP.

18. A message number appears on the
message line. Record the message
number, because in the future, you
may need to reference it.
17
18
Release 4.6A/B
21–14
*HWWLQJ6WDWXVRQ<RXU0HVVDJH
The response to your message is often in the form of an electronic message rather than a
telephone call. It is, therefore, important to monitor the status of your messages.
*XLGHG7RXU


choose Messages to view the status of
your message.
In this section, you can choose one of
the following options:
a. New at SAP is where the message
has been sent to SAPNet but not 1
picked up yet by a SAPNet
consultant.
b. In process by SAP is where an
SAPNet consultant is working on
1a
your message.
c. Inquiry from SAP is where the 1b
SAPNet consultant has a question 1c
for you. To resolve the problem, you
need to respond in a timely manner. 1d
2
d. Solution proposed by SAP is where the
SAPNet consultant has proposed
what they feel is a solution to your
message.
2. For this example, we have a message in
Solution proposed by SAP, so choose this
option.
3. Double-click on your message.

21–15

SAP System Administration Made Easy007

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SAP System Administration Made Easy007

Загружено:

Авторское право:

Доступные форматы

Chapter 17: Change Management

3. Enter the transport command.

The transport log indicates why a transport failed.

System Administration Made Easy

After the transport is completed, check the transport’s exit code:

1. In the Command field, enter transaction SE10 and choose Enter

6. Select the request.

8. On the Import line, check the return

A return code of 8 or higher is a

System Administration Made Easy

10. Choose to drill down for

System Administration Made Easy 18–1

System Administration Made Easy

3. The error message appears in the

1. In the Command field, enter transaction SM51 and choose Enter

System Administration Made Easy

4. Record the Patch level (for our

A support package is an SAP-provided R/3 fix and is similar to an NT Service Pack.

1. From the menu bar, choose System → Status.

3. Choose the Patches tab.

System Administration Made Easy

4. In this example, the following

The name of a Support Package is interpreted as follows:

System Administration Made Easy 19–1

This chapter is an introduction to performance issues in R/3. We provide only general

System Administration Made Easy

Workload analysis is used to determine system performance.

1. In the Command field, enter transaction ST03 and choose Enter

3. Select a time period to analyze.

4. Enter how many minutes back to

5. Under Time interval to be analyzed

System Administration Made Easy

7. Check the Current value under

For more information on Av.

11. Click on any cell in the Response

13. The programs and transactions are

System Administration Made Easy

Create Sales Order VA01

1. In the Command field, enter transaction ST02 and choose Enter

2. The two important things to review on the above screen are:

System Administration Made Easy

To defragment the system’s memory:

Certain operating system items will impact R/3 performance.

System Administration Made Easy

1. In the Command field, enter transaction OS07 and choose Enter

This screen is a snapshot of the CPU,

5. Choose an item under Previous hours

This screen shows CPU utilization

System Administration Made Easy

This window shows the memory

This is the Operating System Log.

Physical access to the drives is the slowest activity.

System Administration Made Easy

System Administration Made Easy 20–1

The prerequisites to use SAPNet–Web are:

1. In your web browser, enter www.sapnet.sap.com.

This main screen (SAPNet for Customers and

System Administration Made Easy

1. In the left frame, scroll down to Services.

The Online Services main screen appears.

If you have a particular problem or question, you should search:

SAP Notes were formerly known as OSS Notes.

2. SAP Notes are divided into several topics. For