SAP BASIS on UNIX and LINUX
SAP BASIS on UNIX and LINUX :
Symbol Legend:
¬ Press Enter
<sid> System ID lower case
<SID> System ID upper case
How do I....?
Backups
Client
Tasks
Communications
Tasks
Database
Tasks
Job
Tasks
Printer
Tasks
Security
Tasks
Support
Package and Binary Patch Tasks
....find your Current SPAM Update and
Support Package Level
System Tasks
Transport
Tasks
User Tasks
Web
and Internet Tasks
Working with the SAP Marketplace
What
do I do if....
....how to find important pages in the SAP
Marketplace?
System Tasks
The normal SAP
instance start up consists of three parts: starting the SAP OS Collector,
starting the Oracle Listener, and starting the SAP instance. The process mainly
goes like this: ora<sid> logs on
and starts the Oracle Listener then
<sid>adm logs on and runs the startsap script.
What? You say we missed a step? What happened to the SAP OS Collector?
The startsap
script takes care of the SAP OS Collector for us. When the SAP Instance starts up via the
startsap script, it checks to see if saposcol is up and running – whether from
the root user starting it manually or from another SAP Instance already
starting it up, it doesn’t matter. If
saposcol is up and running, the script simply moves on to the next step. If it is not, the script starts saposcol as
root and then proceeds. So the SAP OS Collector gets handled one way or
another.
Even if you have
multiple SAP instances on a server, the process is pretty much the same unless
the Oracle databases were installed using the MCOD installation option. Then
only one Oracle Listener is used since both databases share one Oracle listening
port which is normally 1527. Normally
each SAP database – ie SAP instance - has it’s own listener.
Enough talk,
here is how to start a SAP instance.
1.
Verify
that the SAP instance is down.
2.
Log
on to the appropriate server as ora<sid>.
3.
Type
in the following:
lsnrctl start¬
4.
Log
on to the same server as <sid>adm.
5.
Type
in the following – the saposcol will come up automatically:
startsap¬
If you only need to start the database and not the SAP instance too,
type
instead:
startsap DB¬
And do not do the rest of the start up procedures
listed below, you can stop now.
6.
Wait
until the startup messages have scrolled by.
There may be other minor programs that start at the time as well. If you try to logon and are refused
connection, check the logs in the /home/<sid>adm for applicable errors.
The easiest way to confirm that the SAP instance has
started successfully is to log on to the instance. If it has not had a successful start up, look
at the logs in the /home/<sid>adm directory. Sort them witj “ls – ltr” is see the list
sorted in descending order for the ease of viewing.
If nothing obvious is found, go to the
/usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this
directory. The most useful information
can be found in the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files.
If you need further assistance, please refer to the
section SAP
System Start Up Troubleshooting.
The stopping of a SAP instance is
practically the reversal of the start up
Process; stop the SAP instance, stop the
Oracle Listener, and stop the SAP OS
Collector. The only real difference is that the stopsap
script will NOT stop the SAP OS Collector for you, you have to stop that
manually once everything else it down.
There could be other SAP instances still running so the OS Collector
needs to continue to gather information.
1.
Log
on to the appropriate server as <sid>adm.
2.
Type
in the following:
stopsap¬
If you only need to stop the SAP instance and not the database too, type
instead:
stopsap R3¬
And do not do the rest of the start up procedures
listed below, you can stop now.
3.
Log
on to the same server as ora<sid>.
4.
Type
in the following:
lsnrctl stop¬
5.
Log
on to the same server as root.
6.
Type
in the following:
cd /usr/sap/<SID>/SYS/exe/run¬
./saposcol -k¬
7.
Log off the server.
1.
Log
on to the appropriate server as <sid>adm.
2.
Type
in the following:
cd /usr/sap/<SID>/SYS/exe/run¬
./saposcol¬
3.
Log off the server.
1.
Log
on to the appropriate server as <sid>adm.
2.
Type
in the following:
cd /usr/sap/<SID>/SYS/exe/run¬
./saposcol -k¬
3.
Log off the server.
Backups
Backup and
recovery for a SAP instance is best handled along with the other
backup and recovery needs of your
company’s computer systems. But for
those company’s who do not yet possess a solid backup and recovery solution, or
who simply want to segragate the SAP landscape from all other internal IT
solutions, here are a few things you need to know.
Online versus offline, high availability,
frequency, are all decisions your IT staff need to make based on their history
with similar procedures at your company, the recommendations of SAP, and the
guidance of your implementation Basis consultant. Enforced backups, and detailed and tested recovery
procedures should be part of any Disaster Recovery plan, and a documented part
of any SAP implementation project.
If your company falls into the latter
category, SAP does supply tools for your uses which can be used in either line
command form or from within the SAP instance.
If you SAP server contains a tape drive or has access to the network
tape unit, transaction DB13 can be used to
schedule periodic backups. This is the
same transaction where weekly statistics, log cleanup, and database
verification jobs are scheduled in the post-installation work after
installation of a new SAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed in command line
form by the IT staff.
For more information, please see the SAP
Online Documentation for DB13 by going to the
DB13 transaction and clicking Help ->
Application Help or referring to the section Creating Database
Statistics, Index Rebuilds, and Log Backup Jobs – Oracle. More information
regarding BRCONNECT can be found in the SAP BRCONNECT Guide which can be found
at http://service.sap.com/instguides.
What Needs to Be
Backed Up?
The PRD
Instance
Daily backup should be made for these SAP specific
directories:
/usr/sap/<SID>
/sapmnt/<SID>
/usr/sap/trans
on the TMS Domain Controller Server
Any
directories containing flat files that are used by the SAP instance
Daily backups should be made for these Oracle
specific directories:
/oracle
Directory
holding redo logs if not in the /oracle structure
Weekly backup should be made for these OS specific
directories:
Root
/etc
/dev
For Oracle, the entire /oracle directory should be
backed up daily if there is only one Oracle Instance on the server, and each
separate /oracle/<SID> directory if there is more than one instance on
the server.
It is also recommended that a full offline image of
the entire server be made before the monthly closing cycle.
The DEV and
QAS Instances
Weekly backup should be made for these SAP specific
directories:
/usr/sap/<SID>
/sapmnt/<SID>
Any
directories containing flat files that are used by the SAP instance
Weekly backups should be made for these Oracle
specific directories:
/oracle
Directory
holding redo logs if not in the /oracle structure
Monthly backup should be made for these OS specific
directories:
Root
/etc
/dev
For Oracle, the entire /oracle directory should be
backed up daily if there is only one Oracle Instance on the server, and each
separate /oracle/<SID> directory if there is more than one instance on
the server.
It is also recommended that a full offline image of
the entire server be made at the same time every month.
Working with saprouter
Starting
saprouter (OSS Link)
1.
Log
on to the appropriate server as <sid>adm.
2.
Click
Start → Administrative Tools → Services
to open a Services window.
3.
Right-click
on the SAPROUTER service and click Start.
4.
You
may now log off the server.
Verifying the
Status of saprouter
If you have previously successfully
established SAPNet (OSS) communications with SAP via saprouter in the past,
there can only be three reasons for a “broken” SAPNet connection to SAP: the SAP VPN is down (which rarely happens);
your saprouter configuration has been incorrectly changed (also very rare); or
your saprouter is not running (happens all the time).
1.
Log
on to the appropriate server as <sid>adm.
2.
Click
Start → Administrative Tools → Services
to open a Services window.
3.
Look
at the SAPROUTER service. If is not
started, right-click to start the service.
If it is started, right-click & Stop the service and then
right-click & Start the service.
This should “bounce” your saprouter instance.
4.
You
may now log off the server.
1.
Log
on to the appropriate server as <sid>adm.
2.
Click
Start → Administrative Tools → Services
to open a Services window.
3.
Right-click
on the SAPROUTER service and click Stop.
4.
You
may now log off the server.
Not all SAP Notes can be applied via the
SNOTE transaction. Some are information
only, providing no code corrections.
Others entail corrections that can only be done manually. This latter type of SAP Note should be
applied to your SAP system in conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTE change
requests NOT be transported into other systems.
Use the SNOTE transaction in each SAP system that needs the correction,
and delete the generated change requests since they should never be transported
and could lock resources during application of other SAP Notes and support package
application.
If you do not have a working OSS connection, you can download an OSS note from the SAP Marketplace using the
SAP Download Manager and use the upload feature in SNOTE to load it into the
SAP instance instead.
1.
Log
on to client 000 in the appropriate SAP system.
2.
Go
to transaction SNOTE.
3.
On
the Note Assistant - Version XXX/XXXX:
Worklist screen, on the top-most menu bar click Goto → SAP Note download.
4.
On
the Note Assistant: Download Note
popup, type the number of the SAP note in the Note number box and click the clock picture-icon. A SAP
Note XXXXXX is being downloaded message will appear in the bottom status
bar. If you get a communications error
message, verify that saprouter is up and try again.
5.
Once
the SAP Note has been downloaded, it will appear on the Assistant - Version XXX/XXXX: Worklist screen under the SAP Notes →
New navigation tree. The SAP Note can
only be applied if there is a blue box with a black arrow to the left of the
note number. If there is a gray diamond
instead, the downloaded note cannot be applied or is not application for this
SAP system.
6.
To
apply the SAP Note, on the Note Assistant
- Version XXX/XXXX: Worklist screen double click on the downloaded SAP Note
number.
7.
On
the Note Assistant – Display Note XXXXXX
screen, read the note text to see if there are any necessary manual tasks to be
performed after the note is applied.
When you are ready to apply the note, click on the clock picture-icon.
8.
If
there are any prerequisite SAP Notes which need to be applied to the SAP system
before the downloaded SAP Note can be applied, a list will appear in a Load the following notes into your SAP
system popup will appear. Click the
clock picture-icon to download these prerequisite SAP Notes as well. If any of the prerequisite SAP Notes must be
applied in parallel with the original downloaded SAP Note, a list will appear
in a SAP Note queue to be Imported
popup. Click the clock picture-icon to
apply all the listed SAP Notes.
9.
Before
applying any SAP Notes to your SAP system, a Confirmation: SAP Note read popup will appear. Once you have read the information contained
in this popup, click the Yes button.
10.
A
standard Make repairs in foreign
namespaces... popup will appear.
Click the green √ to continue.
11.
On
the Prompt for transportable Workbench
request popup, click the blank page picture-icon to create a new change
request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request
popup which contains the generated change request number for this system
change. Click the green √ to continue.
12.
On
the Confirm changes popup, click the
green √ to continue.
13.
After
the SAP Note has been applied to the SAP system, you will be returned to the Note Assistant - Version XXX/XXXX: Worklist
screen. There is no completion message. Click the green √ and pencil picture-icon.
14.
On
the Set Processing Status for Note XXXXXX
popup, click on the Completed line to
turn “on” the radio button. Click the
green √. You can now leave the SNOTE
transaction. Modified programs,
functions, etc. may require recompilation.
15.
If
the OSS note
you applied changed a ABAP program, you must go to the SE38 transaction and manually recompile the program. If it changed a function, go to transaction SE37 and click the Single Test button – this is enough to force the function to
rebuild and you can back out of the SE37
transaction.
When a SAP instance is first installed,
it comes with an automatical four week license.
But you can’t install any kind of SSCR key on a termporary instance, so
it is best to get the permanent license key immediately.
The license key request process has been
drastically overhauled by SAP over the past.
Normally, if you request a new SAP license key, the information will be
e-mailed to you in the form of a script.
But in case you don’t receive this e-mail promptly, it is important to
know how to obtain the newly generated key “the old-fashioned way”.
1.
Log
on to the server containing the new SAP system as <sid>adm.
2.
Type
the following, pressing enter when you are done:
saplicense -get
3.
You
will see a line reading “saplicense: HARDWARE KEY = XXXXXXXXXXXXXX”. Make note of this information before pressing
Enter.
4.
You
may now log off the server.
1.
Log
on to client 000 of the newly installed SAP system.
2.
Go
to transaction SLICENSE.
3.
From
the top-most menu bar of the SAP License
Administration screen, click Goto → Get hardware key.
4.
On
the Determine Remote Hardware Key
popup, find the host name or IP address for the new SAP system server. Click the button to the left of this entry to
high-bright the line. Click the Detrmne button to continue. The hardware key will appear in the box to
the right of the Detrmne button.
5.
You
may now leave the SLICENSE transaction.
Requesting a New
SAP License Key
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/licensekey.
2.
In
the navigator tree on the right-hand side of the License Keys screen, click on mySAP
Business Suite.
3.
On
the License keys for mySAP Business Suite
screen, click on the Request license key
hyperlink.
4.
On
the License key: Request screen,
click the correct Installation
hyperlink the mySAP Business Suite component.
5.
On
the License key request: System overview
screen, click the New system button.
6.
On
the License key: Request for a new system
screen, fill in the required information in the System section. In the License request section, fill in the Hardware key box right above the Save New Item button. After you have supplied the hardware key,
click the Save New Item button. The license key request will be shifted up to
the first line of the License request
list. Click on the □ to the left of the license request to place a √ in the
box. Now you are finally ready to click
the Send Request button.
7.
You
may now close your web browser session.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/licensekey.
2.
In
the navigator tree on the right-hand side of the License Keys screen, click on mySAP
Business Suite.
3.
On
the License keys for mySAP Business Suite
screen, click on the Display license keys
requested by me hyperlink.
4.
On
the License key: request screen, look
for your requested key. It should appear
with the <SID> you provided during the request process. If the Status
shows as Sent to SAP, the license key
has not yet been generated. If the Status shows as Completed, your new license key has been generated and you can
click on the <SID> System
hyperlink to continue.
5.
On
the License key: request screen,
scroll down until you can see the License
request section. Under the License key header you will see you new
SAP system license key. Write this key
down and remember that it is case sensitive.
Or you can cut-and-paste it to a more convenient storage location.
6.
You
may now close your web browser session.
Applying a SAP
License Key the Old Way
1.
Log
on to the server that contains the new SAP system as <sid>adm.
saplicense -install
2.
You
will be prompted for the <SID>, hardware key, expiration date of the new
license, and the new license. Press Enter
after the entry of each piece of data.
3.
Once
the new license key has been accepted, you will received a License key applied message.
If you have the TXT file SAP e-mailed you, you can place it somewhere on
your server and use the following syntax to install the license as well:
saplicense –install
ifile=<location of TXT file>¬
4. You may now log off the server.
1.
Log
on to client 000 in the SAP system in which the new license key is to be
installed.
2.
Go
to transaction SLICENSE.
3.
From
the top-most menu bar on the SAP License
Administration screen, click Edit → Install license.
4.
On
the Install New License popup, fill
in the new license key you obtained from SAP.
Click network picture-icon to finish the new license installation.
5.
You
will receive a License key successfully
installed message. You may now leave
the SLICENSE transaction.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/sscr.
2.
In
the navigator tree on the right-hand side of the SSCR screen, click on Registration.
3.
On
the SSCR – Registration screen, click
the Register developer radio button
and click an Installation hyperlink. Make sure you select the correct Installation
Number for the SAP “flavor” you need or the generated key will not work.
4.
On
the SSCR – Register Developer screen,
type in the developer’s SAP user ID and click the Register button.
5.
A
new Details section will appear. Note
the generated developer’s key or cut-and-paste for other storage.
6.
You
may now close your web browser session.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/sscr.
2.
In
the navigator tree on the right-hand side of the SSCR screen, click on Registration.
3.
On
the SSCR – Registration screen, click
the Register object radio button and
click an Installation hyperlink. Make
sure you use the MS SQL installation and not R/3.
4.
On
the SSCR – Register Object screen, fill
in the information necessary to generate an object key. If you need help, this information is
contained in the Register Object
popup the programmer received on his workstation. Or, if this is a repair, the information can
be found in the SAP Note containing the advanced correction. Click the Register
button once all information has been enter.
5.
A
new Details section will appear. Note
the generated object key or cut-and-paste for other storage.
6.
You
may now close your web browser session.
Before opening a service connection for
SAP, be sure that the SAPAG client has been added to the appropriate SAP system
and Client, and that a Security Audit Trace has been activated for the SAPAG
ID.
Before a Service Connection to a SAP
server via your saprouter can be created, the saprouter must run the LOP – Line
Opener Program – to initiate the mode of SAP connection. Please LOPInstalltion.exe on your saprouter
server before trying to add and open any Service Connections.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/serviceconnection.
2.
On
the Service Connections screen, click
the Service Connections button.
3.
On
the Service Connections – Overview screen, scroll down the page and find the
SAP instance you want to open. Click on
the red X in that instance’s line.
4.
In
the Enter Data for the system’s semi-automatic opening popup, set the days,
hours, and minutes you want the service connection to stay open. Click the Continue
button.
This part is being rewritten to meet the new SAP
procedures.
Problem Logging with SAP Support
Reporting a Problem to SAP
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights –
2.
On
the Create Customer Messages screen,
click on the Start Message Wizard
button.
3.
On
the Customer messages – Create
screen, click the Select a System
button.
4.
On
the System Selection popup, click on
the + sign next to Show systems to
see a list of your SAP systems registered with SAP. From the expanded list of system, click on
the radio button just left of the <SID> for which you are reporting the
problem. Click the Choose button and you will be returned to the Customer messages – Create screen.
5.
On
the Customer messages – Create
screen, click on the radio button to the left of the System type which has the problem:
development system, test system, or production system. From the Release dropdown, select the appropriate
SAP software release. Click the Continue
hyperlink.
6.
On
the next Customer messages – Create
screen, scroll down to the bottom of the screen. If the problem involves an add-on, select the
appropriate Add-on and Add-on release from the dropdowns; if an
add-on is not involved, leave these dropdowns blank. Verify that the information showing in the Oper. System, Database, and Frontend
dropdowns is correct. If it is not
correct, selection your SAP system’s information from the appropriate
dropdowns. Click the Continue hyperlink.
7.
On
the next Customer messages – Create
screen, scroll down to the bottom of the screen. From the Priority
dropdown, select the appropriate priority of Low, Medium, High, or Very High. From the Component dropdown, select which SAP
component is having the problem. Once
you select a component, a secondary Component dropdown will appear. Select a secondary component and a third
component as well. Do the best you can
to make all three component pieces fit your problem as closely as
possible. Click the Continue hyperlink.
8.
On
the next Customer messages – Create
screen, scroll down to the bottom of the screen. Select a language from the Language dropdown, type a short but
descriptive summary of your problem in the Short
description box, and type a more detailed description of your problem in
the Long test box.
9.
If
there are logs or other files which might assist SAP in resolving the issue,
rename them all so that they have a suffix of “.log” and use the Add attachment hyperlink and the Attachments popup to attach them to the
message. After attaching all the necessary
files, click the Close hyperlink to
return to the Customer messages – Create
screen.
10.
When
you have provided as much information as possible, click the Send to SAP hyperlink.
11.
You
will receive a confirmation screen with a generation problem number. Write this problem number down for later use.
12.
You
may now leave the Message Wizard and
close the web browser window.
Checking the
Status of a Reported Problem
1. Log on to
the SAP Marketplace using an OSS
ID with Administration rights –
2. Click on
Customer Messages. All the open OSS problems you have
sent to SAP
will
appear here.
3. You may
now leave the Message Wizard and
close the web browser window.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button.
4.
On
the Spool Administration: List of Output
Devices screen, click the pencil picture-icon to switch into change
mode. The easiest way to create a new
printer is to copy an existing one.
Click on a similar printer in the output devices screen then click the
create with template picture-icon.
5.
On
the Spool Administration: Create Output
Device screen, fill in the Output
device and Short name. Make any changes that are unique for the new
printer on the Device Attributes and Host Spool Acc Method tabs. When all the required data has been
changed/added, click the Save picture-icon.
6.
You
will receive an Output device was saved
message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate
the printer.
7.
You
may now leave the SPAD transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button.
4.
On
the Spool Administration: List of Output
Devices screen, click the pencil picture-icon to switch into change
mode. Double click on the output device
to be changed.
5.
On
the Spool Administration: Output Device (Change)
screen, make any necessary changes on the Device
Attributes and Host Spool Acc Method
tabs. When all the required data has
been changed/added, click the Save picture-icon.
6.
You
will receive an Output device was saved
message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate
the printer.
7.
You
may now leave the SPAD transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button.
4.
On
the Spool Administration: List of Output
Devices screen, click the pencil picture-icon to switch into change mode. Click on the output device to be deleted and
then click the trash can picture-icon.
5.
On
the Spool admin.: Delete screen, verify
that the correct printer is about to be deleted. Click the Yes
button.
6.
You
will receive an Output device deleted
message in the status bar at the bottom of the screen. You may now leave the
SPAD transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button.
4.
On
the Spool Administration: List of Output
Devices screen, click the pencil picture-icon to switch into change mode.
5.
Click
on an output device to be transported and then click the truck picture-icon.
6.
On
the Spool Administration: List of Output
Devices (Change) popup, click the green √ picture-icon.
7.
On
the Prompt for Workbench request
popup, click the blank page picture-icon to create a new change request. On the Create
Request popup, fill in the Short
description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request
popup which contains the generated change request number for this system
change. Click the green √ to continue.
8.
You
will receive an Entry is made in
transport request message in the status bar at the bottom of the screen. Repeat steps 11 through 14 as many times as
necessary, using the same transport request for all printers.
9.
You
may now leave the SPAD transaction.
If resetting the
printer cache does not clear your printing problem, try using
some a non-SAP
application to print to it to see if it working correctly on the
network. This should at least narrow down the
possibilities.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button.
4.
On
the Spool Administration: List of Output
Devices screen, double click on the printer you need to reset.
5.
On
the Spool Administration: Output Device
(Display) screen, click on the pencil picture-icon to switch from display
mode to change mode.
6.
On
the Administration: Output Device (Change)
screen, on the top-most menu bar click Edit
→ Reactivate.
7.
On
the same Administration: Output Device
(Display) screen, on the top-most menu bar click Edit → Reset Cache.
8.
On
the same Administration: Output Device
(Display) screen, on the top-most menu bar click Edit → NI Reset.
9.
You
may now leave the SPAD transaction.
Local or frontend printing is sometimes
confusing in concept but actually very easy to understand. As a rule, local printer is simply another way of saying that the user is going to print
to the default printer designated on
his/her workstation. You probably do this all the time with Windows to printer spreadsheets, Word documents, etc without thinking about it. You
can do the same thing using SAP.
1. Log on to any client in the appropriate SAP
system.
2. Go to
transaction SPAD.
3. On the Spool Administration: Initial Screen
screen, click the Output Devices
button.
4. On the Spool Administration: List of Output Devices
screen, click the
Change
button and then the Create button.
5. On the Spool Administration: Create Output Device
screen, fill in the
Output Name and Short name - I normally use a short name of “DESK” for
“Desktop
Printing” but alot of people use a Short
name “SWIN” or “LOCL”
as well. Use
the following DeviceAttributes fields:
Device type = SWIN
Device Class = standard printer
And the
following Access Method fields:
Host spool access method = F: Printing
on frontend computer Host
printer = __DEFAULT. That is _ _ D
E F A U L T
Save the printer.
6. You may
now leave the SPAD transaction.
Using this printer will cause print to go to
SAPLPD which will use the default printer of the current workstation.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SP01.
3.
On
the Output Controller: Spool request
selection Screen screen, click on
the Output requests tab.
4.
On
the Output Controller: Output request
selection Screen screen, fill in any information needed to filter the
selection results. Then click on the
clock picture-icon.
5.
A
list of all pending output requests will be displayed.
6.
You
may now leave the SP01 transaction.
Viewing a List of
Output Requests for a Specific Printer
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SPAD.
3.
On
the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output
devices button. On the Spool Administration: List of Output Devices
screen, click on the printer where you need to check the output
requests. Then click on the printer and
page picture-icon.
4.
A
list of all pending output requests for the selected printer will be displayed.
5.
You
may now leave the SPAD transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SP01.
3.
On
the Output Controller: Spool request
selection Screen screen, fill in
any information needed to filter the selection results. Then click on the clock picture-icon.
4.
A
list of all spool requests will be displayed.
Double click on the spool request that is to be reprinted.
5.
Click
on the printer picture-icon. An Output request created message should
appear in the bottom status bar.
6.
You
may now leave the SP01 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SP01.
3.
On
the Output Controller: Spool request
selection Screen screen, fill in
any information needed to filter the selection results. Then click on the clock picture-icon.
4.
A
list of all spool requests will be displayed.
Double click on the spool request that is to be reprinted.
5.
Click
on the printer with a box outline picture-icon.
On the Output controller: Print
spool request XXXX screen, tab down to the line reading Output device and select a new printer. Click on the printer picture-icon.
6.
On
the Output control: Save attributes
popup, click the Yes button.
7.
On
the Confirm redirection of output
popup, click the Yes button. An Output
request created message should appear in the bottom status bar.
8.
You
may now leave the SP01 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SP12.
3.
On
the TemSe --- Administration of Temporary
Sequential Data screen, on the top-most menu bar click TemSe database →
Reorganization.
4.
On
the TemSe --- Administration of Temporary
Sequential Data popup, click the All
TemSe objects older than option to turn “on” the radio button to the
left. Fill in the Days box with “7” for development and quality assurances SAP
systems, and “32” in production SAP systems.
Click the Delete button.
5.
On
the TemSe objects older than XX days
popup, click the Yes button.
6.
After
the successful deletion of the selected temporary objects, you will be returned
to the TemSe --- Administration of Temporary
Sequential Data screen. There is no
task completion message.
7.
You
may now leave the SP12 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SGEN.
3.
On
the SAP Load Generator screen - Generation task section, click on the
line reading Generate all objects in
selected software components to turn “on” the radio button to the
left. Click on the Continue button at the bottom.
4.
On
the SAP Load Generator screen - Selection by software components of
generation set section, click the button to the left of each entry listed
in the Software component box.
Click the Continue button at
the bottom of the screen.
5.
On
the SAP Load Generator screen – Select server for parallel generation section,
there should only be one entry in the Server
box.
Click the button to the left of this entry. Click the Continue
button at the bottom of the screen.
Several messages will appear in the bottom status bar before the next
screen appears.
6.
On
the SAP Load Generator – Job Monitor
screen, fill in the time and date listed under the Schedule job at button located at the bottom of the screen. Click on the Schedule job at button.
7.
On
the SAP Load Generator – Job Monitor
screen – Load generator status section,
the status of mass generation is shown.
You may now leave the SGEN
transaction and later return to check the progress of the recompilation. No other load regeneration jobs can be
scheduled until this one completes. If a
load regeneration jobs fails for some reason, return to the SGEN screen for
instructions on how to restart the job.
The IGS server (Internet Graphics Server) component displays
and generates the graphics used by SAPGui HTML users. For example, the BW users accessing reports
via the internet use the IGS server. The
ITS server also channels graphics through the IGS server. The IGS server is installed as a started
service on each server.
Starting the IGS instance
1.
Log
on to the appropriate server as <sid>adm.
2.
Type
the following:
cd /usr/sap/<SID>/DVEBMGS00/igs¬
./bin/startigs -p . ¬
3.
You
may log off the server.
Stopping the IGS instance
4.
Log
on to the appropriate server as <sid>adm.
5.
Type
the following:
cd /usr/sap/<SID>/DVEBMGS00/igs¬
./bin/stopigs¬
6.
You
may log off the server.
Support Tasks in the SAP
Marketplace
Some adminitrative tasks performed on the
SAP Marketplace are
instantaneous
such as SSCR (SAP Source Correction Registration)
requests for Developer and Object Key,
while others like a
permanent
license key request or registeration of a new OSS ID
1.
You
will need the first and last name, function, department, department title,
language, telephone number, language, and email address of the person(s) being
added as these are all required fields.
2.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/user-admin.
3.
From
the left navigational tree, click on Maintain
User Data → Request new users. You may be asked for your OSS ID and
password again, dependently on your point of original logon.
4.
On
the User Data Maintenance screen, fill
in the gathered information from step #1.
Then press Save. You may or may
not receive a confirmation message.
5.
You
may now log off the SAP Marketplace.
Checking A New
SAP Marketplace User ID aka “S” Number aka OSS ID
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/user-admin.
2.
From
the left navigational tree, click on Maintain
User Data → Display requested users. You may be asked for your OSS ID and
password again, dependently on your point of original logon.
3.
On
the User Data Maintenance screen, you
will see a list of your mostly recently generated OSS IDs. If the user ID you are seeking does not
appear on the screen, you can fill in any of the information allowed in the top
row to performa a search.
4.
Verify
the status of the OSS ID for which you are looking. If the Status
reads Successful, and both the User ID
and Initial Password fields contain
legitmate data, your OSS ID has been generated and you can pass the
information on to your user.
If the Status
reads “Requesting…”, your OSS
ID has not been generated so come
again later to check the status. If the Status makes reference to some type of
error condition, please open an OSS
problem to get it resolved. The normal
turnaround for an OSS ID generation is eight hours or less.
5.
You
may now log off the SAP Marketplace.
Changing the Authorizations for an
Existing SAP Marketplace User ID
aka “S” Number aka OSS ID
***The vast
majority of your OSS ID users have enough privileges to
perform their SAP
Marketplace tasks without any additional rights
granted to their user ID.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/user-admin.
2.
From
the left navigational tree, click on Maintain
User Data → Search and maintain users. You may be asked for your OSS ID and
password again, dependently on your point of original logon.
3.
On
the User Data Maintenance screen, click
Search for an entire list of your SAP
Marketplace users, or fill in the provided fields to help narrow your search,
pressing Search when you are ready.
4.
From
the second User Data Maintenance
screen, click on the Surname of any user you wish to change.
5.
On
the next User Data Maintenance screen,
click on the Authorizations tab, and
then click the Edit button on the
bottom of the displayed section.
6.
From
the resulting User Data Maintenance
Authorization objects overview screen, click on a line you want to change. For example, if you want the OSS
ID to be able to create new OSS problems with SAP, click the Create Customer messages “on” box at the
far left to the line.
7.
On
the resulting User Data Maintenance
Create Customer messages screen, click “on” your option – Customer if you want
the user to be able to open problems for any SAP Instance you own, or select a
specific Installation(s) for only, say, CRM instances.
8.
Click
the Add button at the bottom of th page, and you will be returned to step
#6. Repeat as many times as you need to
do so in order to change the OSS
ID to your requirements.
9.
When
all the changes have been completed, make sure you are at the same screen as in
step #6 and click Save. You should get a screen thanking you and
saying that your changes have been saved.
10.
You
may now log off the SAP Marketplace.
6.
Log
on to any client in the appropriate SAP system.
7.
Go
to transaction RZ10.
8.
On
the Edit Profiles screen, select the
<SID>_DVEBMGS00_SAP<SID> Profile
from the dropdown, or whatever instance profile you need to change. In the Edit
profile section, click the radio button to the left of Extended maintenance. Click
the Change button.
9.
On
the Maintain R/3 Profile screen, click
the Add Parameter button.
10.
On
the next Maintain R/3 Profile screen,
type in the new Parameter name and Parameter val. Click the Copy
button. Click the white arrow on green
picture-icon twice.
11.
On
the Maintain R/3 Profile popup, click
the Yes button to save your changes.
12.
On
the Edit Profiles screen, click the Save
picture-icon.
13.
On
the Save profile popup, click the No button.
14.
On
the Activate profile popup, click the
Yes button.
15.
On
the Edit Profiles popup, click the
green √ button.
16.
On
the Caution! Caution! Caution! popup,
click the green √ button.
17.
If
you receive a Possible Inconsistencies in OP Modes screen, double click over
the <No> unless you are unsure of why this message has been displayed.
18.
You
will not get a confirmation message. You
may now leave the RZ10 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction RZ10.
3.
On
the Edit Profiles screen, select the
<SID>_DVEBMGS00_SAP<SID> Profile
from the dropdown, or whatever instance profile you need to change. In the Edit
profile section, click the radio button to the left of Extended maintenance. Click
the Change button.
4.
On
the Maintain R/3 Profile screen,
locate the parameter that needs to be changed in the Parameter name column.
Change the matching value under Parameter
value to the new value. Click the Copy button. Click the white arrow on green picture-icon.
5.
On
the Edit Profiles screen, click the
Save picture-icon.
6.
On
the Save profile popup, click the No button.
7.
On
the Activate profile popup, click the
Yes button.
8.
On
the Edit Profiles popup, click the green
√ button.
9.
On
the Caution! Caution! Caution! popup,
click the green √ button.
10.
If
you receive a Possible Inconsistencies in OP Modes screen, double click over
the <No> unless you are unsure of why this message has been displayed.
11.
You
will not get a confirmation message. You
may now leave the RZ10 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction RZ10.
3.
On
the Edit Profiles screen, select the <SID>_DVEBMGS00_SAP<SID>
Profile from the dropdown, or
whatever instance profile you need to change.
In the Edit profile section,
click the radio button to the left of Extended
maintenance. Click the Change button.
4.
On
the Maintain R/3 Profile screen, locate
the parameter you need to delete and click on the Parameter name to high-bright it.
On the top-most menu bar, click Parameter
→ Delete.
5.
On
the next Maintain R/3 Profile popup,
make sure that the parameter listed is the one you need to delete. Click the Yes
button to delete the parameter. You will
receive a Parameter was deleted
message in the status bar at the bottom of the screen. Click the Copy
button. Click the white arrow on green
picture-icon.
6.
On
the Edit Profiles screen, click the
Save picture-icon.
7.
On
the Save profile popup, click the No button.
8.
On
the Activate profile popup, click the
Yes button.
9.
On
the Edit Profiles popup, click the
green √ button.
10.
On
the Caution! Caution! Caution! popup,
click the green √ button.
11.
If
you receive a Possible Inconsistencies in OP Modes screen, double click over
the <No> unless you are unsure of why this message has been displayed.
12.
You
may now leave the RZ10 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM50.
3.
On
the Process Overview screen, all
processing threads for the SAP system are displayed. If a thread is being used, the name of the
report running will be displayed as well as the number of seconds that the
report has been running, the client in which the report is running, the action
the report is currently doing, and, if applicable, the table the report is
currently accessing.
4.
Click
on the blue arrow circle picture-icon to refresh the process data appearing on
the screen.
5.
Click
the white clock picture-icon to display the amount of CPU time consumed by each
process thread so far.
6.
Double
click any display line containing a report name in order to see more detailed
information about the running report.
This information includes database access statistics and timings. Use the white arrow on green picture-icon to
go back to the Process Overview
screen.
7.
Click
on any process thread and then click the blue cylinder with glasses picture-icon. This will display the Trace Data screen which shows the actual communication between SAP,
the operating system, and the database server.
This information is useful when tracking process thread problems. Use
the white arrow on green picture-icon to go back to the Process Overview screen.
8.
You
may now leave the SM50 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM50.
3.
On
the Process Overview screen, find the
process which must be
stopped. Place a √ in the □ to the left of the process
number
to be
stopped by pressing Space. On the
top-most menu bar,
click the Process → Cancel without core.
4. Click the
blue arrow circle picture-icon to refresh the Process
Overview screen until the stopped
process has cleared from the
display.
4.
You
may now leave the SM50 transaction.
If this does not kill the process, you
can go to transaction SM04 and kill the user’s session. If this does not kill the process, you can
log on to the server, open a Task Manager session, and End the Process. If this does not kill the session, there is
an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice
but to “bounce” the SAP instance and/or possibly the serve.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction RZ10.
3.
On
the Save profile popup, click the No button.
4.
On
the Edit Profiles screen, select the
<SID>_DVEBMGS00_SAP<SID> Profile
from the dropdown, or whatever instance profile you need to change. In the Edit
profile section, click the radio button to the left of Extended maintenance. Click
the Change button.
5.
On
the Maintain R/3 Profile screen,
locate the dialog processes rdisp/wp_no_dia
line in the Parameter name
column. Change the matching value under Parameter value to the new value. Click the Copy
button. Do the same for the batch processes, rdisp/wp_no_btc, and the update processes, rdisp/wp_no_vb. Be sure to
click the Copy button after each
change. When all the changes have been made, click the white arrow on green
picture-icon.
6.
On
the Edit Profiles screen, click the
Save picture-icon.
7.
On
the Save profile popup, click the No button.
8.
On
the Activate profile popup, click the
Yes button.
9.
On
the Edit Profiles popup, click the
green √ button.
10.
On
the Caution! Caution! Caution! popup,
click the green √ button.
11.
If
you receive a Possible Inconsistencies in OP Modes screen, double click over
the <No> unless you are unsure of why this message has been displayed.
12.
You
will not get a confirmation message. You
may now leave the RZ10 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM02.
3.
On
the System Messages screen, click the
Create button.
4.
On
the Create System Messages popup,
type up to 3 lines of System message text. Select a server (there should only be one)
from the Server dropdown. If you want to limit the message to one
client, select a client from the Client
dropdown. If desired, fill in an Expiry date and/or Delete date. Click the green
√ to save the message.
5.
A
System message added message will
appear in the bottom status bar. You may
now leave the SM02 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM02.
3.
On
the System Messages screen, double
click on the Id number of the message
that needs to be changed.
4.
On
the Display System Messages popup,
click the pencil and glasses picture-icon to switch to change mode.
5.
On
the Change System Messages popup, make
your changes and click the green to save the changed message.
6.
A
System message changed message will
appear in the bottom status bar. You may
now leave the SM02 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM02.
3.
On
the System Messages screen, click on
the Id number of the message to
highlight the message that needs to be deleted.
Click the Delete button.
4.
On
the System message: Delete popup,
click the Yes button to delete the
message.
5.
A
System message deleted message will
appear in the bottom status bar. You may
now leave the SM02 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SE37.
3.
On
the Function Builder: Initial Screen screen,
type in the Function name
“TH_POPUP”. Click the Single Test wrench picture-icon.
4.
On
the Test Function Module: Initial Screen
screen, fill in User, Client, and Message Text.
Click the clock picture-icon. The
message will be sent to the specified user.
5.
You
may now leave the SE37 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM01.
3.
On
the Transaction Code: Lock/Unlock
screen, you will see an empty box at the very bottom of the screen. Type in the transaction code you want to lock
and press Enter.
4.
The
transaction code to be locked should appear at the top of the transaction
list. Place a √ in the □ to the left of
the transaction to be locked by pressing Space.
Press Enter.
5.
The
transaction is now locked. You may now
leave the SM01 transaction.
Short dumps care generated when one of the SAP
programs encounters an “abnormal” condition, a condition that the program was
not coded to handle in any of its error routines. While it is not a function of the Basis
support team to “debug” SAP programs, familiarity with some of the dump
sections can be valuable for SAP Note searches and/or logging system problems
with SAP.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction ST22.
3.
On
the ABAP runtime errors screen, you
can click the Today button for
today’s dumps, the Yesterday button
for yesterday’s dumps, or use the Own
Selection section of the screen to narrow down your time date/time range
and then click the Start you selection
button.
4.
On
the List of Selected Runtime Errors
screen, double-click on any short dump
you want to examine more closely.
5.
On
the Runtime Error Long List screen, make note of the error that occurred in the
What Happened? section, any unique
information in the Error analysis
section, and search terms for searching SAP Notes in the How to correct the error section.
6.
You
may now leave the ST22 transaction.
Viewing
Database Lock Information
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction DB01.
3.
The
information displayed on the Oracle Lock Monitor screen can be sorted and
filtered to meet your reporting requirements.
4.
You
may now leave the DB01 transaction.
Viewing
Table Lock Information
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM12.
3.
On
the Select Lock Entries screen, fill
in the Table name or use *, the Client or use *, and the User name or use *. Click the List
button.
4.
On
the Lock Entry List screen, you can
use the Refresh button to monitor the
table locks, or double-click any line for detail information. You can also use this transaction to delete a
table lock or all table locks, if necessary.
5.
You
may now leave the SM12 transaction.
Viewing
Update Lock Information
Occasionally, due to a
dropped user session or some other unknown
reason, an update transaction fails. When this happens, locks
placed on resources may not be
released. If an object was marked
as currently being updated, and the update
fails, the lock may
still be present in the SAP system. Any other transactions
attempting
an update on the “locked” object fail.
Database errors,
including SAPSQL_ARRAY_INSERT_DUPREC
errors, appear in the system
log.
To remove these update locks, you should try to force the
update to complete. If the update cannot be forced to completion,
the lock should be removed from the
object.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM13.
3.
On
the Update Records: Main Menu screen,
if you are looking for the update locks produced by a specific user and/or in a
specific client, type in the Client
and/or User. Using a From
date and To date range can help
as well. But if the originating lock
happened some time ago, using a date range will not help. Normally, there aren’t that many “hanging”
update locks at one time, so don’t worry about being too specific. When you have entered all your information,
press Enter.
4.
The
Update Records screen contains a list
of outstanding update records matching your selection criteria. If the list is empty, go back to the previous
screen and open your search by using “*” in client and user, and a date range
of 01-01-2000 through 12-31-2010. If you
still get no results, there are no incomplete update records.
5.
The
best way to resolve incomplete update records is to try to force them to
completion. From the top-most menu of
the Update Records screen, click Update records → Update → All records.
6.
You
will see an Update – Updating update
requests which have not yet executed popup.
If, after reading this information message, you decide that deleting the
update records would be a wiser decision, skip to step 7. Otherwise, click the green √
picture-icon. You will be given one last
chance to stop via a Update selected
records popup. Click Yes to start the update.
7.
If
the update records are fairly old (a day or so) and/or the update force
produces an error, or you are unsure whether forcing the update record to
completion is the wisest choice, forcing the update may not be an option. If this is the case, deleting the update lock
is probably your best course of action.
From the top-most menu of the Update
Records screen, click Update records → Delete → All records. You will be given an opportunity to change
your selection criteria in the Delete
Update Records popup. Click the
green √ picture-icon to continue. You
will be given one last chance to stop via a Delete
data will be lost popup. Click Yes to start the delete.
8.
You
will not receive a confirmation message after the update or delete. You may now leave the SM13 transaction.
The SAP directory structure
on a Linux server can be viewed via SAP using the AL11 transaction. All the usual SAP directories are accessible
as well as any custom data views. Text
files can be accessed and ported in and out of the SAP instance. Directories can be sorted by Name or
Date/Timestamp.
Transport Tasks
Note:
if you already have a TMS configured, do not use this section to add a
new instance to the existing TMS configuration.
You could severely damage any pre-existing transports, making them
untransportable. Instead, use the
following section Adding New Instance to TMS Setup.
1.
Log on to client 000 of the SAP instance to serve as the Domain
Controller.
2.
Go to transaction SE06.
3.
Click on the Perform Post
Installation Actions button.
4.
Go to transaction STMS.
5.
You should see a popup box with the title TMS: Configure Transport
Domain. If the popup doesn't say that, press F6 to change to the
correct popup box.
6.
Fill in the TMS: Configure
Transport Domain popup with the
Description, Name of DOMAIN_<SID>, and the description of the
Transport Domain. Then click Save.
7.
On the Transport Management
System screen (if you aren’t there, back out until you are), assuming that
this is the first SAP instance and there are no other
installed SAP instances in your landscape yet, and assuming that you
want your transport requests to be transportable and not local only,
click on Overview → Systems.
8.
On the System Overview –
Domain Domain_<SID> screen, click SAP
System → Create → External System. Fill in QAS if you are
going to have a three system configuration or PRD if you are going to have a
two system configuration, or make up a <SID> if you are never really
going to have another SAP system. Fill in the rest of the information including
the Path which is assumed to be
\\<current server>:\usr\sap\trans for NT or /usr/sap/trans for UNIX.
Click Environment → Transport Routes.
9.
On the Display Transport
Routes screen, click the User Settings button, turn “on” the Hiergraphical List Editor,
and click the √ Continue button. Back out of the screen and then go back in –
you should see the list in a text mode which makes it easier to handle.
10. On the Display Transport Routes screen, click the
Display<>Change button to
toggle into Change Mode.
11. On the Change Transport Routes screen, click Configuration → Standard Configuration → Development
and Production System.
12. Fill in the Development and Production System popup,
using your current SAP system SID as the Development
system and the SAP instance you created in step #8 as the Production system. Click the √ mark to Continue.
13. Back on the Change Transport Routes screen, click
the Save icon and confirm all the
popup questions.
14. On the Change Transport Routes screen, back out
until you can once more see the Transport
Management System screen. Click Overview → Systems.
15. On the Display TMS Configuration: System XXX
screen, double-click the TMS Domain domain controller SAP instance.
16. On the Display TMS Configuration: System XXX
screen, click the Display<>Change
button to toggle into Change Mode. Click the Communication tab and make sure
that the Transport Group Name is
correct. It should contain of the Domain
Controller in the format of DOMAIN_<SID> where <SID> is the System
ID of the SAP Domain controller. Use the
dropdown to find the correct entry it the field is blank. Click the Transport
Tool tab. Verify that the
information on the tab is correct and click the Insert Row button. Add a Parameter of CTC and a Value of 1. Click the Save
button.
17. Do step #16 for
every system in your TMS Domain, making sure to change all Transport Group Names are the same and the CTC row is added to each
with a value of 1.
18. Save your way
back the the main STMS screen.
19. You may now
leave STMS.
1.
Log on to client 000 in the
SAP instance you want to add to the existing TMS
Domain.
2.
Go to transaction SE06.
3.
Click on the Perform Post Installation Actions
button.
4.
Go to transaction STMS.
5.
You should see a popup box
with the title TMS: Configure Transport
Domain. Press F6 until you see a TMS: Include System in
Transport Domain popup.
6.
Fill in the TMS: Include System in Transport Domain
popup with the
Description,
Target Host, and System number of the TMS Domain
Controller then click Save.
7.
You should see a message
that says SAP System waiting to be
included in the Transport Domain.
8.
Log on to client 000 of the
Transport Domain Controller and go to transaction
STMS, keeping your original session in the
other SAP instance open.
9.
On the Transport Management System screen, click Overview → Systems.
Highlight the System you just added and then
click SAP System → Approve.
Then confirm all the messages.
10. Back on the Transport Management System screen, click Environment →
Transport Routes.
11.
On the Display Transport Routes screen, click the Display<>Change button
to toggle into Change Mode. Click on Edit
→ Transport Route → Create.
11. On the Create Transport Route
popup, use the Consolidation boxes to
enter
the SID of the transport domain, create a Z* transport layer, and the
SID
of the system you are adding. Click Save
and confirm. Back out to the main
Transport Management Screen.
12. Back on the Transport Management System screen, click Overview → Systems.
Double-click on
the new system, and click on the Communications tab. Make
sure that the
Transport Group name is the name of the original transport
domain. If not,
change it. Click the Transport Tool
tab. Verify that the
information on
the tab is correct and click the Insert
Row button. Add a
Parameter of CTC and a Value of 1. Click the Save button.
13. You can switch back to the new instance, and
confirm that the SAP System
waiting to be included in the Transport Domain
has
disappeard.
14. You may now
log out of both SAP instances.
Sometimes, mistakes just
happen. For this example, we will use a
transport
SM1K00047 as the erroneous
change request. Make sure to release
SM1K00047 before
beginning this procedure.
1. Log on to the client who is
the owner of the local transports that needs fixed.
2. Go to SE03.
3. On the Transport
Organizer List screen, click on Merge Object Lists which is
in the Requests/Tasks section.
3. On
the Merge Objects List screen, put SM1K00046 in the first Request/Task
field. Make sure that the Released
check box is "on" in the Request Status
section and click the Execute icon.
4. On the Merge Objects
List screen, click on the Merge icon.
5. On the Enter Transport Request popup, click the Create Request icon.
6. On the Select Request Type popup, click "on" radio buttion Workbench
Request.
7. On the Create Request popup, fill in the necessary information and
make sure
that the fill in the Target field so
that the transport request is NOT local.
Click the Save, OK, √ icon, etc. until
everything is done. You will
get a new transport request number, in our
case SM1K00050. This new request
can be released using one of the transport
organizer Transactions like SE10,
etc. Once it is released, you can go to /usr/sap/trans
on the OS level and in
directory cofiles copy K00050.SM1 to
K00046.SM1, and in directory data copy
R00050.SM1 to R00046.SM1.
8. You may now leave SE03.
Once you have control of
your session again, the transports are done.
Verify their return code in the Import Queue list. It shoud have been updated automatically.
Transporting
Change Requests
To manually transport change
requests from DEV/QAS to PRD:
1.
Make
sure the change request(s) has been released via Se10 or one of the other
Transport Organizer Transactions.
2.
Go
to transaction STMS and click Overview → Imports. Double-click the PRD queue.
3.
Click
the refresh button to make sure you have the most current view of the PRD
queue. Make sure the change request(s)
you want to transport shows in the queue.
4.
Using
the F9 button, highlight all the transactions you want to manually transport.
5.
Click
on Extras → Activate Inactive Requests.
Confirm the popup. This bypasses
the STMS_QA process.
6.
Leave
the change requests highlighted. Click
Request → Import. On the popup, make
sure that the target is client 300. Make
sure that Synchronous radio button is "on" in the Execution tab. Make sure that the first three options are
checked "on" in the Options tab.
When you are done, click on the green √ and confirm the next popup.
Once you have control of
your session again, the transports are done.
Verify their return code in the Import Queue list. It shoud have been updated automatically.
1.
Make
sure the change request(s) has been released via Se10 or one of the other
Transport Organizer Transactions.
2.
Go
to transaction STMS and click Overview → Imports. Double-click the PRD queue.
3.
Click
on Extras → Other Requests → Add. Fill
in the Number of the Transport Request to be added to the queue and then press
Enter.
4.
Confirm
the Add Transport Request popup. The
transport request should now appear at the bottom of the queue list.
1.
Go
to transaction STMS and click Overview → Imports. Double-click the queue for which you want to
view the history.
2.
Click
on the Import History button or press Ctrl+F7.
The resulting list can be sorted and filtered to produce a more exacting
report if needed.
1.
Go
to transaction STMS and click Overview → Imports. Highlight the queue into which the
transport(s) to be moved again were originally
transported – the “FROM” queue - and click the Import History button or
press Ctrl+F7.
2.
If
your SAP instance is older, you may have a very long Import History list in the
next screen. Use some of the available
filters and sort options to create a more controllable list of transports. Use the F9 to select and/or unselect as many
as you need to transport.
3.
Once
all choices have been made, click Request → Forward → System. Fill in the “TO” system and click on the
Execute green √ mark.
4.
Now
you can go to the “TO” queue and refresh the list. Your imports should all be there.
1.
Go
to transaction STMS and click Overview → Imports.
2.
On
the Import Overview screen, click Import Queue → Check → Transport Tool. You may get a message asking if you want to
check the the transport tool for all systems.
If only want to check a limited subset of the SAP instances, use F9 to
select and/or deselect those systems before you click Transport Tool.
3.
On
the TMS: Check Transport Tool screen, a list of all selected SAP instances to
be checked will appear.
If you see any thing but red green Oks, expand all
the lines with the non-OK marks and look for more information. Correct these problems and then run this
report again until it comes back clean.
1.
Log on to client 000 of your TMS Domain
Controller SAP Instance.
2.
Go to transaction STMS.
3.
On the Transport System Management screen,
click Overview -> Transport
Routes.
4. On the Display
Transport Routes screen, click the Display<>Change
button to
toggle
into Change mode. Click on the Target Groups line and click the
Create button.
5. In the Create
Transport Group popup, fill in the Target
Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the
Target Group name must start and end with a “/”.
6. Enter each Target system and Target client you
need. For our example, we will
DEV 100, QAS 200, and QAS 210. Click the green check mark to Transfer. You
now have a target group. Now you must
create a Consolidation Layer.
7. Back on the Change Transport Routes screen, click on Transport Routes and
click Create.
8. In the Create Transport Route
popup, click the Extended Transport
Control
button at the bottom of the popup. Make sure Consolidation
is "on" and fill
in the information using our Target Group as the Consolidation
Target.
9. Click the green check button to Save the change.
10.
You now have a Transport Group. Confirm
the Disturbution of it to the other
SAP Instances.
A Quality Assurance system must have a)
a delivery route leading from it to
another instance, and b) be the target
of a consolidation route. See topic
Using Target
Groups to Transport to Mulitple Clients in Two Different Instances
to fulfill the a) requirement.
1.
Log on to client 000 of your TMS Domain
Controller SAP Instance.
2.
Go to transaction STMS.
3.
On the Transport
System Management screen, click Overview
-> Transport
Routes.
4. On the Display Transport Routes screen, click Display<>Change button to
toggle
into change mode. Click on the instance
in which you want to control
QA. Normally, this is QAS and the instance to be
controlled is PRD. Under
Transport Routes, click on the QAS
instance and click Create.
5. On the Create
Transport Route screen, make sure Delivery is "on" and fill in
Source and
Delivery systems with QAS and PRD. Click
the green check mark to
save.
Now you have met condition a.
6. Back on the Change Transport Routes screen, click on the QAS instance and
click the single pencil Change button. You will see a Change System
Attributes popup. Click "on"
Quality Assurance - Delvery After
Confirmation.
If you want to change the people who OK the
transports, click the
Procedure
button and make your changes. Then back out.
Click the green check
to Transfer your changes.
7. Back on
the Change Transport Routes screen, click on the Target Groups
line
and click the Create button.
8. In the Create Transport Group popup, fill in the
Target Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the
Target Group name must start and end with a “/”. Enter each Target
system and Target client you need. Click the green check mark to Transfer.
You now have a target group. Now you must create
a Consolidation Layer.
9. Back on the Change Transport Routes screen, click on Transport Routes and
click
Create.
10. In
the Create Transport Route popup, click
the Extended Transport Control
button at the bottom of the popup. Make sure Consolidation
is "on" and fill
in the information using our Target Group as the Consolidation
Target. Click
the green check button to Save the change.
11.
You now have a Transport Group. Confirm
the Disturbution of it to the other
SAP Instances.
12. You
may now leave the STMS transactions.
1. Log on to client 000 of your TMS Domain Controller
SAP Instance.
2. Go to
transaction STMS.
3. On the Transport System Management screen,
click Overview -> Imports.
Double-click on the queue for the SAP instance are
in.
4.
On the Import
Queue screen, click the Refresh
button. Click on the Import
All Requests button.
5. On the Start
Import popup, fill in the information for the
job. Make sure "At
Start
Time" is on. Although Period appears grayed out, you can still change
it to the periodic value you need. I recommend
every hour in DEV, 4 times a
day in QAS, and once an evening in PRD. Click on the green check mark to
Continue.
6. You may now
leave the STMS transaction. If you ever need to change this job,
you must do it via STMS and
not SE37.
User Tasks
1.
Log
on to the appropriate SAP system and the client where the new user is to be
added.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the new User name and
click the blank page picture-icon.
4.
On
the Maintain User screen, fill in at
least the following information for each tab:
Address Last name, First name, Internet mail
Logon data Initial
password, repeat password, user type
Defaults Decimal
formation, Date formation, Time zone, OutputDevice
Roles Select roles to be added to the user
Profiles Select profiles to be added to the user
When all necessary data has been entered, click the Save
picture-icon.
5.
You
will receive a User saved message in
the status bar at the bottom of the screen.
You may now leave the SU01
transaction.
1.
Log
on to the appropriate SAP system and the client where the user is to be
changed.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the User name to be
copied and click the double blank page picture-icon.
4.
On
the Copy User popup, type in the To for the new user and click the Copy button.
5.
On
the Maintain User screen, click on
the tabs and make the changes to the user’s information. When you are done, click the Save
picture-icon. You will receive a User saved message in the status bar at
the bottom of the screen.
6.
You
may now leave the SU01 transaction.
Modifying a User
7.
Log
on to the appropriate SAP system and the client where the user is to be
changed.
8.
Go
to transaction SU01.
9.
On
the User Maintenance: Initial Screen
screen, type in the user’s name and click the pencil picture-icon.
10.
On
the Maintain User screen, click on
the tabs and make your user information changes. When you are done, click the Save picture-icon.
11.
You
will receive a User saved message in
the status bar at the bottom of the screen.
You may now leave the SU01
transaction.
1.
Log
on to the appropriate SAP system and the client where the user is to be
deleted.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the user’s name and click the trash can picture-icon.
4.
On
the Delete user popup, click the Yes button.
5.
You
will receive a User deleted message
in the status bar at the bottom of the screen.
You may now leave the SU01
transaction.
1.
Log
on to the appropriate SAP system and the client where the user is to be locked.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the user’s name and click the lock/unlock picture-icon.
4.
On
the Lock user popup, click the lock picture-icon.
5.
You
will receive a User locked message in
the status bar at the bottom of the screen.
You may now leave transaction SU01.
1.
Log
on to the appropriate SAP system and the client where the user’s password is to
be changes.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the user’s name and click the lock/unlock picture-icon.
4.
On
the Change Password popup, enter the
new password in both the New password
and Repeat password boxes. Click the green √ picture-icon.
5.
You
will receive a The password was changed
message in the status bar at the bottom of the screen. You may now leave the SU01 transaction.
1.
Log
on to the appropriate SAP system and the client where the user needs the role.
Go to transaction SU01.
2.
On
the User Maintenance: Initial Screen
screen, type in the user’s name and press Enter to confirm that the user
exists.
3.
Click
the Change button or press Shift+F6.
4.
On
the Maintain User screen, click on
the Roles tab. Fill in the name(s) in
the field(s) provided, and when done press Enter.
5.
Click
the Save button.
6.
Go
to transaction PFCG, and on the Role Maintenance screen, type in the
name of the role to which the users where added and press Enter to confirm
exist of the role.
7.
Click
the Change role little yellow pencil button.
8.
On
the Change Roles screen, click the User tab. Click on User
Comparison and then Complete
Comparison. Once the comparision is
done, click Save one more time and you are done!
Making user changes one-at-a-time can be
extremely time consuming not to mention boring.
SAP has provided mass change transaction to help eleviate the
tediousness of making many user changes.
It should be noted, however, that the mass change transaction is limited
as to the changes that can be made. For
example, you cannot change the password for multiple users. Also note that it is best to make one type of
mass change at a time. For example, you
need to add a new role to and delete an existing role from 20 users. The best method to achieve this would be to
first do a mass change to add the new role.
Save the changed users. Then delete
the existing role from the same 20 users.
1.
Log
on to the appropriate SAP system and the client where the user changes are to
take place.
2.
Go
to transaction SU10.
3.
On
the User Maintenance: Mass Changes
Initial Screen screen, you need to select whether you will select users
based on Address Data or Authorization Data and click the
appropriate button. If you click Address Data, you can find users with
any combination of First name, Last name, User ID, Company, City, Building, Room, Extension, Department, and Cost Center. If you opt to use Authorization Data, you can specify a combination of Groups, Reference User, Authorizations, Athorization Objects, and many other
fields. For either method, fill in the
fields you want to search on in the Users
by Complex Selection Criteria screen, and click the Execute button.
4.
On
the Users by Complex Selection Criteria
screen, you can click “on” the users to be changed, or click the Select All button. Once all the users you want to change have
been selected, click the Transfer
button.
5.
Back
on the Maintenance: Mass Changes Initial
Screen screen, you can select all the users on the screen again by clicking
the Select All button or change your
mind and make any last minute corrections.
Once you have all the users selected that you want to change, click User
→ Change.
6.
On
the Mass User Changes screen, scroll
through the tabs, changing data and clicking the Add or Remove button for
each correction. Please note, each SU10
batch run must use all Adds or all Removes but never a mixture. Do all Adds
in one run and then all Removes in
another. Once all your changes have been made, click the Save button.
7.
On
the Mass changes popup, you will see
how many users you are about to change.
To make the changes, click on Yes.
8.
On
the Log Display screen, you will see
a log of the changes you made. Expand
the list to see the transactional details.
9.
You
may now leave the SU10 transaction.
1.
Log
on to the appropriate SAP system and client where the user reports are to be
generated.
2.
Go
to transaction SUIM.
3.
On
the User Information System screen,
click the Infosystem authorizations
entry on the navigation tree and click the double arrows pointing down
picture-icon to expand the list of available reports.
4.
Click
on the clock picture-icon to the left of the report you want to run. You will be taken to a selection filter
screen to customize the data you need to see on your report. Once your report has been produced, you can
print it or send it to your hard disk.
5.
You
may now leave the SU01 transaction.
User Information Repository Reports
6.
Log
on to the appropriate SAP system and client where the user reports are to be
generated.
7.
Go
to transaction SU01.
8.
On
the User Maintenance: Initial Screen
screen, from the top-most menu bar click Information
→ Information system.
9.
On
the User Information System screen,
click the Infosystem authorizations
entry on the navigation tree and click the double arrows pointing down
picture-icon to expand the list of available reports.
10.
Click
on the clock picture-icon to the left of the report you want to run. You will be taken to a selection filter
screen to customize the data you need to see on your report. Once your report has been produced, you can
print it or send it to your hard disk.
11.
You
may now leave the SU01 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM04.
3.
On
the User List screen, all users
currently logged on to the SAP system are displayed. To delete a user’s session, place a √ in the
□ to the left of the user to be dropped and click the Sessions button.
4.
On
the Overview of Sessions popup, click
on the session No to be deleted. Click the End
Session button.
5.
You
will not receive a deletion confirmation message. You may now leave the SM04 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM19.
3.
From
the top-most menu bar on the Security
Audit: Administer Audit Profile screen, click Profile → Create.
4.
On
the Create new profile popup, type in
a new Profile name and click the
green √ picture-icon.
5.
On
the Filter 1 tab of the Security Audit: Administer Audit Profile
screen, click the □ to the left of Filter
active to place a √ in the box. In
the Selection criteria section,
select the Clients and User names to be traced. In the Audit
classes section, click “on” all the auditing functions you need for this
profile. In the Events section, click the radio button to the left of the level of
auditing you need. Once you have entered
all your trace information, click the Save picture-icon. You will receive an Audit profile saved in the status bar at the bottom of the screen.
6.
Please
note that while the user trace has been saved, it is not yet active. To activate the user trace, see the next
section Activating a User Audit Profile.
7.
You
may now leave the SM19 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM19.
3.
On
the Security Audit: Administer Audit
Profile screen, select the audit profile to be activated from the Profile dropdown. Click the lit match picture-icon to activate
it. You will receive an Audit profile activated for next system
start in the status bar at the bottom of the screen. The audit will not begin until after the SAP
instance has been recycled.
4.
You
may now leave the SM19 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM19.
3.
On
the Security Audit: Administer Audit
Profile screen, select the audit profile to be deactivated from the Profile dropdown. From the top-most menu bar, click the Profile → Deactivate. You will
receive a Current audit profile was
deactivated in the status bar at the bottom of the screen.
4.
You
may now leave the SM19 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM19.
3.
On
the Security Audit: Administer Audit
Profile screen, select the audit profile to be deleted from the Profile dropdown. Click the trash can picture-icon.
4.
On
the Confirmation prompt popup, click
the Yes button. You will receive an Audit profile deleted in the status bar at the bottom of the
screen.
5.
You
may now leave the SM19 transaction.
1.
Log
on to any client in the appropriate SAP system.
2.
Go
to transaction SM20.
3.
In
the Selection, Audit classes, and Events
to select sections of the Security Audit
Log: Local Analysis screen, provide your information to filter the audit
information. If you need to trace the
activities of a specific user, be sure to include that user’s ID. Click the Re-read
audit log button.
4.
The
resulting list is displayed. This list
can be printed using the usual methods.
5.
You
may now leave the SM20 transaction.
Security Tasks
The easiest way to create a
new user role is to copy an already existing user role, either one of your own
or one of the ones provided to you in the installation of SAP. So let’s assume that you have none of your
own and use one of the SAP role templates provided. It might assist you with picking one of these
roles if you have someone dump the appropriate information into a spreadsheet
containing the Role Name, Role Description, Transactions contained in the Role,
and the Transaction description. The SQL
query would be something like this:
SELECT
AGR_TEXTS.AGR_NAME, AGR_TEXTS.TEXT, AGR_TCODES.TCODE, TSTCT.TTEXT
FROM AGR_TEXTS, AGR_TCODES, TSTCT
WHERE AGR_TEXTS.MANDT = '000' AND
AGR_TEXTS.SPRAS = 'E' AND
AGR_TEXTS.LINE = 0 AND
AGR_TCODES.MANDT = '000' AND
AGR_TCODES.AGR_NAME =
AGR_TEXTS.AGR_NAME AND
TSTCT.SPRSL = 'E' AND
TSTCT.TCODE = AGR_TCODES.TCODE
ORDER BY AGR_TEXTS.AGR_NAME, AGR_TCODES.TCODE;
This query should be changed
based on the details of your SAP instance.
Identify the roles(s) to be used as the source for your role copy.
1.
Log
on to client needing the role.
2.
Go
to transaction PFCG.
3.
On
the Role Maintenance screen, either type in the role name to be copied or
select it from a dropdown. Press Enter
to confirm that the role exists.
4.
Click
the Copy role button or press Shift+F11.
5.
One
the Query popup box, fill in the to role field
with the name to be given the new role.
Come up with a standard that everyone follows so the base original role
is designated in some way so you don’t forget where you got the original. The name must begin with Z or Y. Most people
will add a Z- in the first two characters of the role name. If you want to only select specific roles
from a Composite role, you would click the Copy selectively button, otherwise
click the Copy all button.
6.
Once
the role has been copied, you will be taken back to the original PFCG screen where you will see the name
of your new role. Change you Role
description and save the new role before working with it any further
1.
Log
on to client needing the role change.
2.
Go
to transaction PFCG.
3.
On
the Role Maintenance screen, either
type in the role name to be changed or select it from a dropdown. Press Enter to confirm that the role is
found.
4.
Click
the Change Role little yellow pencil
button role button or press F6.
5.
Click
the Authorizations tab and then the Change Authorization Data button.
6.
On
the Change Role: Authorizations
screen, expand and change the authorizations you need to adjust. When finished click first the Save button and
then the Generate button – looks like a little red and white beachball.
7.
Back
out to the Change Roles screen and click the User tab. Click on User Comparison and then Complete
Comparison. Once the comparision is
done, click Save one more time and you are done!
1.
Log
on to client needing the role deletion.
2.
Go
to transaction PFCG.
3.
On
the Role Maintenance screen, either type in the role name to be changed or
select it from a dropdown. Press Enter
to confirm that the role is found.
4.
Click
the Role Delete button or Shift+F2.
5.
On
the Delete Role popup, confirm that you wish to delete the deletion. If you get an Information popup, confirm it
also.
6.
Your
deletion will return a successful message in the bottom status bar.
Transporting User
Roles between Clients (Transport System Method)
When a modification is made to a role in the 100
client, the roles must be transported to the 800 client. One role, several roles, or all roles can be
done if needed. They can all be added to
the same transport change request. After
the roles have been moved to other clients, you will need to log on to each of
those clients and do a user comparison.
You will also need to do a text comparison in client 100 of the
appropriate SAP system.
1.
Log
on to client 100 of the appropriate SAP system.
2.
Go
to transaction PFCG.
3.
On
the Role maintenance screen, type in
the Role name of the first role to be
transported. Click the Truck
picture-icon.
4.
You
will see an Information popup. Click the green √ picture-icon.
5.
In
the Choose objects popup, unclick the
□s beside User assignment and Personalization. If you want to transport the users along with
the role, profiles, and authorizations, you can √ the □ to the left of User assignment. Click the green √ picture-icon.
6.
On
the Prompt for Customizing request
popup, click the blank page picture-icon to create a new change request. On the Create
Request popup, fill in the Short
description and click the Save picture-icon. You will be returned to the Prompt for Customizing request popup
which contains the generated change request number for this system change.
Click the green √ to continue.
7.
You
will see a Data entered in change request
message in the status bar at the bottom of the screen. Now enter the name of the next role to be
transported and click the Truck picture-icon.
8.
You
will see an Information popup. Click the green √ picture-icon.
9.
In
the Choose objects popup, unclick the
□s beside User assignment and Personalization. If you want to transport
the users along with the role, profiles, and authorizations, you can √ the □ to
the left of User assignment. Click
the green √ picture-icon.
10.
On
the Prompt for Customizing request
popup, continue to use the same transport you created in step 6. Click the green √ to continue.
11.
Continue
to perform steps 7 through 10 until all the roles you need to transport have
been attached to the transport change request.
12.
The
generated transport can now be released and transported into the clients
needing the modified roles.
13.
You
may now leave the PFCG transaction.
Transporting User Roles between Clients
(Upload/Download Method)
Central User Administration distributes clients and
their information to the other clients connected to the Distribution
Model. It does not, however, do the same
for roles and role authorizations. So
when a modification is made to a role in the 100 client, the roles must be
transported to the 800 client. One role,
several roles, or all roles can be done if needed. They can all be added to the same transport
change request. After the roles have
been moved to other clients, you will need to log on to each of those clients
and do a user comparison. You will also
need to do a text comparison in client 100 of the appropriate SAP system.
1.
Log
on to client 100 of the appropriate SAP system.
2.
Go
to transaction PFCG.
3.
On
the Role maintenance screen, type in
the Role name of the first role to be
transported. Click the Truck
picture-icon.
4.
You
will see an Information popup. Click the green √ picture-icon.
5.
In
the Choose objects popup, unclick the
□s beside User assignment and Personalization. If you want to transport the users along with
the role, profiles, and authorizations, you can √ the □ to the left of User assignment. Click the green √ picture-icon.
6.
On
the Prompt for Customizing request
popup, click the blank page picture-icon to create a new change request. On the Create
Request popup, fill in the Short
description and click the Save picture-icon. You will be returned to the Prompt for Customizing request popup
which contains the generated change request number for this system change.
Click the green √ to continue.
7.
You
will see a Data entered in change request
message in the status bar at the bottom of the screen. Now enter the name of the next role to be
transported and click the Truck picture-icon.
8.
You
will see an Information popup. Click the green √ picture-icon.
9.
In
the Choose objects popup, unclick the
□s beside User assignment and Personalization. If you want to
transport the users along with the role, profiles, and authorizations, you can
√ the □ to the left of User assignment.
Click the green √ picture-icon.
10.
On
the Prompt for Customizing request
popup, continue to use the same transport you created in step 6. Click the green √ to continue.
11.
Continue
to perform steps 7 through 10 until all the roles you need to transport have
been attached to the transport change request.
12.
The
generated transport can now be released and transported into the clients
needing the modified roles.
13.
You
may now leave the PFCG transaction.
Performing a User Comparison on the
Modified Roles
1.
Log
on to client 100 of the appropriate SAP system.
2.
Go
to transaction PFCG.
3.
On
the Role maintenance screen, type in
the Role name of the first role to be
transported. Click the Change button.
4.
On
the Change Roles screen, click the User tab.
5.
On
the User tab, click the User compare button.
6.
On
the Compare Role User Master Record
popup, click the Complete compare
button.
7.
You
will receive a User master record for
role was adjusted message in the status bar at the bottom of the
screen. You may now leave the PFCG transaction.
Performing a Text Comparison to Refresh Role
Selection Lists
1.
Log
on to client 100 of the appropriate SAP system.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, type in the user “model_user”.
Click the pencil picture-icon.
4.
On
the Maintain User screen, click the Text comparison from child Syst. button.
5.
On the CUA: Text comparison from Child Systems screen, type “LSDEV100” for
the Receiving system and “LSQAS800”
for the to system. This is a range, and since LSPRD300 falls
alphabetically between LSDEV100 and LSQAS800, all three systems will have the
text comparison performed. Click the
clock picture-icon.
6.
On
the CUA: Text comparison from Child
Systems results screen, you will see a list of the systems compared and the
compare results. Click the white arrow
on green picture-icon 3 times, or until you have left the SU01 transaction.
Users, Roles, and Authorizations
SAP security is based on authorization objects and
authorizations. An authorization object
is used to indicate that a user can perform a certain activity. An authorization is used to limit the scope
of that activity.
For example, a profile contains the S_DEVELOP
authorization object. This authorization
object allows a user to perform ABAP workbench activities. Some users will need to do all ABAP activities
while others will only need to perform a few.
So S_DEVELOP has a selection of authorizations you can use: ACTVT, DEVCLASS, OBJNAME, OBJTYPE, and
P_GROUP. The authorizations are set to
the appropriate values as needed. A tree
view of the S_DEVELOP authorization object can be seen below:
S_DEVELOP
ACTVT
Create
or generate
Change
Display
Delete
Activate,
generate
Execute
Create
in DB
Delete
in DB
Convert
to DB
Administer
Copy
All
Functions
Deactivate
Mod. assistant
DEVCLASS
Single
Value or Value Range
OBJNAME
Single
Value or Value Range
OBJTYPE
Single
Value or Value Range
P_GROUP
Single
Value or Value Range
The S_DEVELOP authorization object in a profile lets
a user perform ABAP workbench activities.
But having a S_DEVELOP authorization object with the ACTVT authorization
value set to Display (03) means that the user is limited to display only in the
ABAP workbench transactions. Thus we see
that authorization objects grant while authorizations limit. It is important to remember, however, that a
user with a profile having a S_DEVELOP with full authorizations still cannot
access an ABAP workbench transaction until a matching S_TCODE (start up
transaction code) has been added as well.
In other words, a user may have the rights to add, modify and delete
ABAP programs but until an entry for SE38 has been added to the S_TCODE
authorization object, he cannot access transaction SE38 which is the ABAP
Editor.
All authorization objects and authorizations are
grouped into profiles before being attached to users. Profiles use a combination of authorization
objects and their respective authorizations, and their creation can be complex
as well as tedious. In order to simplify
the creation of profiles, the Profile Generator (transaction PFCG) was
created. Roles are created via a more user-friendly
interface which generates profiles based on the information added via this
interface.
Manually creating profiles is the “old” way of doing
things. There are times, such as the
start of a new SAP landscape where no roles exist, that the use of profiles is
handy. But once the landscape has been
completed all users, with the exception of the Basis team, should be attached
to roles. There should never be a need
to manually create a SAP new profile. To
add a new role, the easiest method is to copy an existing role that matches
your needs as closely as possible and make the changes you need for the new
role.
This documentation covers changing user security via
both methods.
Remember that
profiles are NOT the standard way to implement SAP security
1.
Log
on to the appropriate client in the appropriate SAP system.
2.
Go
to transaction SU02.
3.
In
the Manually edit authorization profiles
section of the Profile: Initial Screen
screen, enter the Profile you want to
change. Make sure the Active only □ is checked. Click the Create
work area for profiles button.
4.
On
the Profile List screen, double-click
the profile to be changed.
5.
A
profile can contain authorization objects only (single profile) or one or more
other profiles (collective profile). If
the next screen is titled Maintain
Profile, this is a single profile, and you should proceed to the next step. If the next screen is titled Collect Profiles, this is a collective
profile and you should skip to step 13.
6.
On
the Maintain Profile screen, you must
decide if you need to add a new authorization object and one or more of its
authorizations, or add a new authorization to an authorization object already
in the profile. If you need to add a new
authorization to an authorization object already in the profile, skip to step
7. Otherwise, scroll down the Consisting of authorizations list until
you find a blank line. Type the
authorization object you need to add and press Enter. You will need to scroll through the list
again until you find the authorization object you just added (it is was to find
since the Authorization column should
still be blank). Once you find the new
entry line, use the drop down to fill in the Authorization column. Click
on the Save picture-icon.
7.
If
you need to add another authorization to an authorization object already in the
profile list, click on the +Add
authorization button.
8.
From
the Maintain Profiles: Object Classes
screen, double-click the Object class
of the authorization you are adding.
9.
On
the Maintain Profiles: List of
Authorizations screen, select the authorization you need to add by
double-clicking the appropriate line.
This will return you to the Maintain
Profile screen where you can see that your authorization has been added.
10.
On
the Maintain Profile screen, click
the Save picture-icon. Then click the
lit match picture-icon to activate the new profile changes.
11.
On
the Activate Profile: Execution Screen
screen, click on the lit match picture-icon to complete the profile activation
process.
12.
You
may now leave the SU02 transaction.
13.
In
order the change a profile collection, you must make the changes in one or more
of the dependent profiles, save the changes in the dependent profile(s),
activate the dependent profile(s), save the collection owner profile, and
activate the collection owner profile.
On the Collect Profiles
screen, double-click on the profile you want to change.
14.
You
will be taken to the Maintain Profile
screen. Perform steps 6 to 11. Then use the white arrow on green picture-icon
to go back.
15.
On
the Collect Profiles screen, click
the Save picture-icon. Then click the
lit match picture-icon to activate the new profile changes.
16.
On
the Activate Profile: Execution Screen
screen, click on the lit match picture-icon to complete the profile activation
process.
17.
You
may now leave the SU02 transaction.
Adding Authorization
Objects and/or Authorizations to a Role
1.
Log
on to client 100 in the DEV SAP system.
2.
Go
to transaction PFCG.
3.
On
the Role Maintenance screen, enter
the Role you want to change. Click the Change
button.
4.
On
the Change Role screen, click the Authorizations tab and then click the
pencil picture-icon.
5.
If
you are only adding a start up transaction to the role, skip to step 10. Otherwise, the assumption is that a new
authorization object is to be added. On the Change
role: Authorizations screen, click the +Manually
button.
6.
On
the Manual selection of authorizations
popup, enter the authorizations objects that need to be added (ie S_DEVELOP,
S_PROGRAM, etc.) Click the green √ when
you are finished.
7.
Back
on the Change role: Authorizations
screen, if all the displayed signal lights are green, skip to step 8. Otherwise, fully expand the lines that are
yellow and/or red and supply the necessary information. All signal lights should be green before
moving to the next step.
8.
On
the Change role: Authorizations
screen, click the Save picture-icon. You
will receive a Data saved
confirmation message in the status bar at the bottom of the screen.
9.
On
the Change role: Authorizations
screen, click the red-and-white beach ball picture-icon to generate a profile
from the saved role. Reply affirmatively
if any confirmation popups. You will
receive a Profile(s) created message
in the status bar at the bottom of the screen.
If you do not need to add any start up transactions to the profile, you
may now leave the PFCG transaction.
10.
On
the Change Role: Authorizations
screen, expand the Cross-application
Authorization Objects → Authorization
Check for Transaction Start → Authorization
Check for Transaction Start until you see the Transaction code entry line.
Double-click on the entry portion of the Transaction code line.
11.
In
the Maintain Field Values popup,
scroll down the list until you find a blank From
and To line. Enter the transaction(s) to be added, and
click the Save picture-icon when you have finished.
12.
On
the Change role: Authorizations
screen, click the Save picture-icon. You
will receive a Data saved
confirmation message in the status bar at the bottom of the screen.
13.
On
the Change role: Authorizations
screen, click the red-and-white beach ball picture-icon to generate a profile
from the saved role. Reply affirmatively
if any confirmation popups. You will
receive a Profile(s) created message
in the status bar at the bottom of the screen.
14.
You
may now leave the PFCG transaction.
*** Since SAP R/3 4.5, this is not the standard for
user authorizations.
***
Granting Transaction Access to a User via
Role
1.
Log
on to the applicable SAP instance and client.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, fill in the User ID for the
user you want to change, either by typing it in or choosing it from the drop
down. Click the little yellow pencil Change button.
4.
On
the Maintain User screen, click on
the Roles tab. Fill in the new role in the first available Role field. Press ENTER to confirm that the role
exists. Click the Save button.
5.
Make
sure to use transaction PFCG to run
a user comparion to rebuilt the role-to-user connections.
6.
You
may now leave the PFCG transaction.
*** Since SAP R/3 4.5, this
is not the standard for user authorizations.
***
Revoking
Authorizations from a User via Role
Use the same procedure as Adding Authorization Objects and/or Authorizations to a
Role
Revoking
Transaction Access from a User via Profile
*** Remember that profiles
are NOT the standard way to implement SAP security. ***
Attaching a
Profile to a User
*** Since SAP R/3 4.5, this
is not the standard for user authorizations.
***
Attaching a Role
to a User
1.
Log
on to the applicable SAP instance and client.
2.
Go
to transaction SU01.
3.
On
the User Maintenance: Initial Screen
screen, fill in the User ID for the
user you want to change, either by typing it in or choosing it from the drop
down. Click the little yellow pencil Change button.
4.
On
the Maintain User screen, click on
the Roles tab. Fill in the new role in the first available Role field. Press ENTER to confirm that the role
exists. Click the Save button.
5.
Make
sure to use transaction PFCG to run
a user comparion to rebuilt the role-to-user connections.
6.
You
may now leave the PFCG transaction.
Client Tasks
*** SAP’s terms for the sending and receiving
clients can be confusing. The “target”
client is the client into which data is to be copied. The “source” client is the client which
contains the data to be copied. Also,
remember that all client copies are destructive and will delete all data before
copying in the new data. The only
exception is when the SAP_USER profile is used.
In this case, only user master data is deleted from the target client
before the new user master data is copied.
***
1.
Create
the target client if necessary.
2.
Log
on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for
the user and “pass” for the password.
3.
Go
to transaction SCCL for Local Client
Copy.
4.
On
the Client Copy – Copy a Client
screen, use the Selected profile dropdown
to select a profile that matches your needs.
Use SAP_ALL or SAP_UAPP to copy all data except change
documents, SAP_USER to copy only user
master data, or one of the other SAP provided client copy profiles. Type the Source client and Source client user masters in the provided boxes. These two boxes should contain the same
client number unless the data is to come from one client and the user master
data from a different client. Once all
information has been provided, click the Schedule
as background job button. If you
receive a Change documents will not be
copied message in the bottom status bar, click the green √ next to the
transaction command field at the very top of the screen to continue.
5.
On
the Schedule Client Copy in Background
screen, use the Background server
dropdown to select the background server on which the job is to run. There should only be one server available in
the dropdown. Click the Schedule job button.
6.
On
the Verification popup, check that
everything is correct and click the Continue
button.
7.
On
the Start Time popup, if you want the
client copy job submitted right away, click the Immediate button. To
schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time.
If you are unsure as to the format of date and time, click on the
top-most menu bar System → User profile → Own data. Click on the
Defaults tab to see your default date format.
If the user is SAP* due to a new client, you may receive a date
validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY,
MM/DD/YYYY, YYYY.MM.DD, YYYY/MM/DD, and YYYY-MM-DD. Click the Save picture-icon.
8.
On
the Background Print Parameters
popup, select an Output device from
the dropdown. Click the green √ to
continue.
9.
You
will receive a client copy confirmation message. You can monitor this copy by using
transaction SCC3. You may now leave the SCCL transaction.
*** SAP’s terms for the sending and receiving
clients can be confusing. The “target”
client is the client into which data is to be copied. The “source” client is the client which
contains the data to be copied. Also,
remember that all client copies are destructive and will delete all data before
copying in the new data. The only
exception is when the SAP_USER profile is used.
In this case, only user master data is deleted from the target client
before the new user master data is copied.
***
1.
Create
the target client if necessary.
2.
Log
on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for
the user and “pass” for the password.
3.
Go
to transaction SCC9 for Remote
Client Copy.
4.
On
the Client Copy – Copy a Client
screen, use the Selected profile dropdown
to select a profile that matches your needs.
Use SAP_ALL or SAP_UAPP to copy all data except change
documents, SAP_USER to copy only user
master data, or one of the other SAP provided client copy profiles. Since this
is a client copy that uses data from a client in another SAP system (or remote
client), a Source destination must be
provided. This is a RFC connection
pointing to a specific client in another SAP system. If there is no RFC connection to the client
you wish to copy, you will need to create one.
Otherwise, use the dropdown to select the remote source client. To test that your select Source destination
RFC connection will work, click the RFC
system check button. Once the proper remote source client has been
selected, the System name and Source client boxes will fill
automatically. Once all information has
been provided, click the Schedule as
background job button. If you
receive a Change documents will not be
copied message in the bottom status bar, click the green √ next to the
transaction command field at the very top of the screen to continue.
5.
On
the Schedule Client Copy in Background
screen, use the Background server
dropdown to select the background server on which the job is to run. There should only be one server available in
the dropdown. Click the Schedule job button.
6.
On
the Verification popup, check that
everything is correct and click the Continue
button.
7.
On
the Start Time popup, if you want the
client copy job submitted right away, click the Immediate button. To
schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time.
If you are unsure as to the format of date and time, click on the
top-most menu bar System → User profile → Own data. Click on the
Defaults tab to see your default date format.
If the user is SAP* due to a new client, you may receive a date
validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY, MM/DD/YYYY,
YYYY.MM.DD, YYYY/MM/DD, and YYYY-MM-DD.
Click the Save picture-icon.
8.
On
the Background Print Parameters
popup, select an Output device from
the dropdown. Click the green √ to
continue.
9.
You
will receive a client copy confirmation message. You can monitor this copy by using
transaction SCC3. You may now leave the SCC9 transaction.
Sometimes you
need to retain the data residing in a client but refresh the roles, users, and
other security components that have changed in DEV client 100. Since role changes don’t transport across the
other clients maintained via Central User Administration, a user master client
copy can be used on any client in the SAP landscape.
1.
Log
on to the appropriate client on the appropriate SAP system.
2.
If
the user master data is coming from a client within the same SAP system, go to
transaction SCCL. If the user master data is to be copied from
a client in another SAP system, go to transaction SCC9.
3.
On
the Client Copy – Copy a Client
screen, use the Selected profile
dropdown to select profile “SAP_USER”. Type in the same client for both the Source client and Source client user masters. This
should be the client that contains the user master data you want to copy. If this is a user master copy that uses data
from a client in another SAP system (or remote client), a Source destination must be provided. Once all information has been
provided, click the Schedule as
background job button. If you
receive a Change documents will not be
copied message in the bottom status bar, click the green √ next to the
transaction command field at the very top of the screen to continue.
4.
On
the Schedule Client Copy in Background
screen, use the Background server
dropdown to select the background server on which the job is to run. There should only be one server available in
the dropdown. Click the Schedule job button.
5.
On
the Verification popup, check that
everything is correct and click the Continue
button.
6.
On
the Start Time popup, if you want the
client copy job submitted right away, click the Immediate button. To
schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time.
If you are unsure as to the format of date and time, click on the
top-most menu bar System → User profile → Own data. Click on the
Defaults tab to see your default date format.
Click the Save picture-icon.
7.
On
the Background Print Parameters
popup, select an Output device from
the dropdown. Click the green √ to
continue.
8.
You
will receive a client copy confirmation message. You can monitor this copy by using
transaction SCC3. You may now leave the SCCL or SCC9 transaction,
whichever is appropriate.
1.
Log
on to any client in the “target” SAP system.
2.
Go
to transaction SCC3.
3.
On
the Client Copy/Transport Log Analysis
screen, click the All clients button.
4.
From
the list of Client copy logs, double
click on a client to view summary information for all client copies where this
client was the target client. Double
click on any of these summary lines to see statistics for a particular copy
client job.
5.
You
may now leave the SCC3 transaction.
*** Before adding a new client you should first ask
if it will be used in communications with other clients (Central User
Administration, source for client copies, etc.)
If so, the new client will need to be assigned a Logical System ID that
is unique among all the SAP systems in the landscape. It is recommended that all new clients be
assigned to a Logical System ID as soon as they are created. ***
1.
Log
on to any customizable client in the appropriate SAP system.
2.
Go
to transaction SCC4.
3.
On
the Display View “Clients”: Overview
screen, click the pencil and glasses picture-icon to switch into change mode.
4.
On
the Display View “Clients”: Overview
popup, click the green √ to dismiss the informational message.
5.
On
the Change View “Clients”: Overview
screen, click the New Entries button.
6.
On
the New Entries: Details of Added Entries
screen, fill in Client number and
description and the City. Use the Logical
system dropdown to assign a logical system ID to the client. Type “USD” in the Std currency box. Select a Client role from the client role
dropdown (remember that there can only be one Productive client per SAP
system). In the Changes and transports for client-specific objects, Client-independent object changes, Protection: Client copier and comparison
tool, and Restrictions when starting
CATT and eCATT sections, select the necessary restriction levels from the
provided dropdowns. Once all information
has been provided, click the Save picture-icon.
7.
You
will see a Data saved in the status
bar at the bottom of the screen. You may
now leave the SCC4 transaction.
1.
Log
on to the client to be deleted.
2.
Go
to transaction SCC5.
3.
On
the Delete Client screen, verify that
you are deleting the correct client. If
you also want the client deleted for T000 (ie the scc4 entry), put a √ in the □
to the left of Delete entry from T000
by clicking the □. Click the Background button.
4.
On
the Schedule Client Copy in Background
screen, use the Background server
dropdown to select the background server on which the job is to run. There should only be one server available in
the dropdown. Click the Schedule job button.
5.
On
the Verification popup, check that
everything is correct and click the Continue
button.
6.
On
the Start Time popup, if you want the
client delete job submitted right away, click the Immediate button. To
schedule the delete for a later date and/or time, click the Date/Time button. In the Date/Time
section, provide the Scheduled start Date
and Time. If you are unsure as to the format of date
and time, click on the top-most menu bar System
→ User profile → Own data. Click on the Defaults tab to see your default
date format. Click the Save
picture-icon.
7.
On
the Background Print Parameters popup,
select an Output device from the
dropdown. Click the green √ to continue.
8.
You
will receive a client copy confirmation message. Don’t panic, it looks like a client copy
confirmation and says nothing about this being a delete job. You can monitor this copy by using
transaction SCC3. You may now leave the SCC5 transaction.
When adding a new client to a SAP system,
the information listed in
the SCC4 can be confusing. This is a brief explain of the
available client
restrictions.
Client role:
The category indicates the
role of the client in your R/3
system.
Possible roles are:
* Production client
* Test client
* Training client
* Demo client
* Customizing client
* SAP reference client
This field should be
maintained by the customer for
Documentary
purposes. Release 3.0 also ensures the following:
If
there is a productive client in the target system, no client copy (remote copy)
which also selects cross-client customizing objects may be imported into the
system. If cross-client settings are imported, inconsistencies may occur in all
clients.
In
a productive client, customizing settings that can be maintained as
"current settings" can be excluded from a client lock or transport
links; this means current settings (e.g. exchange rates, posting periods) can
always be maintained in a productive client without recording changes. SAP is
planning to link further effective functionality to this flag, to enable
adequate protection of a productive client in a system with further (test)
clients.
Other
settings for a client:
Change and
transports for Client Dependent Objects
Changes
without automatic recording – the client can be customized although the system
will not generate change requests.
Automatic
recoding of changes – the client can be customized and all changes are
generated into change requests.
No
changes allowed – no modifications can be made to the client – it is protected
or locked. This is the usual
configuration for a production client where customization should not be
performed.
No transports allowed – changes are allowed but cannot be
transported.
Client-Independent Object
Changes
Changes
to repository and client-independent customizing allowed – no restrictions on
this client for changes and development.
No
changes to client-independent customizing objects - allows for development on
repository objects but not client-independent customizing.
No
changes to repository objects – lets users perform client-independent
customizing but no development or modifications to repository objects.
No
changes to repository and client-independent customizing objects – this setting
prohibits any client-independent modifications and is common on Production
systems.
A logical system gives a
client a unique “name” which can be referenced by other clients within the SAP
landscape. Once you have created a
logical system, use the SCC4
transaction to assign the logical system to a client. Normally, you create the logical system
before creating a client so that both start out together. Adding a logical system to a client after the
client has been in existence and in use to a long time period could cause
referencing problems between that client and the rest of the SAP systems.
1.
Log
on to any customizable client in the appropriate SAP system.
2.
Go
to transaction SALE
Application Link Enabling (ALE)
Sending and Receving Systems
Logical Systems
Define Logical System
4. On the Display IMG screen, click the clock
picture-icon to the
left of Define Logical System.
5. On the Display IMG popup, click the green √
button to dismiss
the informational message.
6.
On
the Change View “Logical Systems”:
Overview screen, click the New
Entries button.
7.
On
the New Entries: Overview of Added Entries screen, fill in the Log. System and Name. The logical system should match the naming convention already
in place: LS<SID><Client
Number>, such as “LSDEV100” for DEV Client 100. The description should be uniform as well
such as “Logical System for DEV Client 100”.
Click the Save picture-icon.
8.
On
the Prompt for Workbench request
popup, click the blank page picture-icon to create a new change request. On the Create
Request popup, fill in the Short
description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request
popup which contains the generated change request number for this system
change. Click the green √ to continue.
9.
You
will receive a Data saved message in
the status bar at the bottom of the screen.
You may now leave the SALE
Communications Tasks
1.
Log
on to any client on the appropriate SAP system.
2.
Go
to transaction SM59.
3.
On
the Display and maintain RFC destinations
screen, click the Create button.
4.
On
the RFC Destination screen, type in a
RFC destination name. This name should contain meaningful
information such as the SID of the SAP system and/or any client numbers. Select the Connection type from the connection type dropdown, and type the
connection specifics in the Description
box. If the connection type is a “3”
(another SAP system), fill in the necessary client logon information in the Logon section. Fill in the Language, Client, User, and Password for an existing user in the target RFC SAP system. This user should be a system or communication
user (ie RFC_USER or ALEREMOTE), not a dialog user. Once all this information is provided, press
Enter.
5.
In
the Technical settings section of the
RFC Destination screen, type in the
name or IP address of the Target host. If the target is another SAP system, enter
the number of System number (00 for
all SAP systems except BW QAS which needs a 01). Press Enter.
6.
On
the RFC Destination screen, click the
Save picture-icon. You will receive a Destination saved message in the status
bar at the bottom of the screen. You may
now leave the SM59 transaction.
1.
Log
on to any client on the appropriate SAP system.
2.
Go
to transaction SM59.
3.
On
the Display and maintain RFC destinations
screen, expand the appropriate RFC
destination navigation level and double click the RFC destination to be
changed.
4.
On
the RFC Destination screen, make any
necessary changes. Once the information
is changed, click the Save picture-icon.
5.
You
will receive a Destination saved
message in the status bar at the bottom of the screen. You may now leave the SM59 transaction.
1.
Log
on to any client on the appropriate SAP system.
2.
Go
to transaction SM59.
3.
On
the Display and maintain RFC destinations
screen, expand the appropriate RFC
destination navigation level and click the RFC destination to be deleted. Click the Delete
button.
4.
On
the Delete destination popup, click
the Yes button.
5.
You
will not receive a confirmation message.
You may now leave the SM59
transaction.
Database Tasks
Database statistics refresh jobs should
be scheduled to run twice daily on all the SAP systems. But occasionally a manual refresh needs to be
done due to table reorganization, index rebuild, etc.
1.
Log
on to the server using the <sid>adm user ID.
2.
Open
the MS SQL Server Enterprise Manager.
3.
Expand
the navigator tree until you see the Management entry. Expand it.
4.
Right-click
on Database Maintenance Plans and click New Maintenance Plan.
5.
Use
the wizard to create the job you need.
6.
You
may now close the Enterprise Manager session and log off the server.
1.
Log
on to the appropriate SAP instance any client.
2.
Go
to transaction DB13.
3.
On
the DBA Planning Calender for Oracle
Database <SID>: Maintain screen, double-click on a blank line on any
day in the future.
4.
On
the Schedule Action for <Day>.
DD.MM.YYYY popup, use the radio
button to turn “on” the task you want to do.
For each action, you need to fill in the Start Time in military time format, the Period (Weeks) which is how many weeks between running of this job
– blank for one time only, 1 for weekly, 2 for bi-weekly, etc. and Calender if you want to use any calendar
except the SAP supplied standard Factory calendar.
These are the details for
each action:
Whole
database offline + redo log or
Whole
database offline backup or
Whole
database online + redo log or
Whole
database online backup
Generic tape names for database backup
Database backup profile – usually
init<SID>.sap
Options for ReDo log backup
Redo
log backup
Generic tape names for database backup
Options for ReDo log backup
Partial
database offline backup or
Partial
database online backup
Tablespace names to be included in the
back up
Generic tape names for database backup
Database backup profile – usually
init<SID>.sap
Check
and update optimizer status
Tablespace names to be included in the
statistics run
Adapt
next extents
Tablespace names for next extents adaption
Check
database
N/A
Verify
database
Tablespace names to be verified
Database backup profile – usually
init<SID>.sap
Cleanup
logs
N/A
5.
You
may now leave the DB13 transaction.
1. Log on to the appropriate SAP instance and
client using BATCH_USER.
2. Go to transaction SM36.
3. On the Define
Background Job screen, fill in the Job
name field with the new job name.
Select a Job Class priority of
A for High, B for Medium, and C for Low.
It is SAP’s recommendation that all client-owned jobs begin with a Z for
identification purposes. And most Basis
people recommend the next two characters be the initials for the SAP module for
which the SAP instance runs. Like ZBC*
for a Basis job, and ZHR* for a Human Resources job. Click on the Specify start condition button or press F5.
4. On the Start
Time popup, click the Immediate
button to start the job right away, or click the Date/Time button to specify a date/time in the future for which the
job run. Click “on” the Periodic job radio button and then click
the Period values button if you want
to schedule to job to run on a periodic basis.
Provide the periodic values and click Save back to the main Define
Background Job screen.
5. On the main Define Background Job screen, click the Step button.
6. On the Create
Step 1 popup, fill in the ABAP
program Name and any Variant
needed to run the program – you had to have created the variant using
BATCH_USER before using it here. Then
click Save once more.
7. Back on the Define Background Job screen, check that all the job information is
correct and then click the Save
button one last time.
1. Log on to the appropriate SAP instance and
client as either the user ID owning the job or an administrator ID.
2. Go to transaction SM37.
3. On the Simple
Job Selection screen, fill in the Job
name field or use any of the screens filtering options to produce a list
from which you can see the job to be changed.
In order for a job to be changed, it has to have a status of Schedule or Released so turn those statuses “on” and turn the rest “off”. Click on the Execute button.
4. On the Job
Overview screen, click “on” the line containing the job to be changed and
then click Job → Change.
5. On the Change
Job screen, make your changes and then click Save. If you have more than
one occurance of the same job in your list, you must change each job scheduled
to run earlier than that job you just changed.
Once the job you changed runs, all occurences of the jobs running after
that date will be changed as well.
1. Log on to the appropriate SAP instance and
client as either the user ID owning the job or an administrator ID.
2. Go to transaction SM37.
3. On the Simple
Job Selection screen, fill in the Job
name field or use any of the screens filtering options to produce a list
from which you can see the job to be deleted.
In order for all occurances of a job to be deleted, all statuses of the
job should be checked “on”. And enter an
all-encompassing date like 01-01-1990 through 12-31-2010. Click on the Execute button.
4. On the Job
Overview screen, click “on” all the perpetent line containing the job(s) to
be deleted and then click on the Delete
job from database button.
5. On the Delete
Scheduled Jobs? popup, confirm the deletion.
1. Log on to
the appropriate SAP instance and client as either the user ID owning the job or
an administrator ID.
2. Go to
transaction SM37.
3. On the Simple Job Selection screen, fill in the
Job name field or use any of the
screens filtering options to produce a list from which you can see the job you
want to view. In order for all
occurances of a job to be viewed, all statuses of the job should be checked
“on”. Click on the Execute button.
Deleting an
Active aka Runaway Job
Opinions on this
topic vary so these are good guidelines to use.
These are
pretty much in
the order they should be tried:
1. Kill the session via SM37 or SM04.
2. Try End session through SM50 or cancel program from SM66.
3. If the Work Process in SM50 is in stopped state then killing
it will not help much or quickly, you need to identify why it is stopped
(running a program on another server, runing in parallel etc.) Try and end
those.
4. Kill Work Process in SM50 without core.
5. Kill process or PID via program
RSBDCOS0.
6. If all else fails, restart the SAP
instance server.
The most important things to remember when killing a WP are:
1. Change to restart = no as otherwise the session can jump back in sometimes
as most of its memory is not actually living in the WP.
2. Allow it a long time to stop, there is no need to do it twice or
50 times as I have seen some people do, the poor old thing is just trying to
recover rollback and reinitialize itself.
1. Log on to the appropriate SAP instance and
client.
2. Go to transaction SE38 and type in Program
name RSBTCDEL and click on the Execute
button.
3. On the Delete
batch jobs screen, fill in the filtering information you need. It is suggested that Delete with forced mode be “on”.
Click on the Execute button.
4. A status message will appear in the bottom
Status Bar as the list of job logs to be deleted is built. Once all the specified job logs have been
deleted, a final total of jobs logs cleaned will appear in the bottom Status
Bar.
In order to apply new support packages and kernel
patches to a SAP system, several preparation steps are required:
·
Checking
for new SPAM updates, support packages and kernel patches
·
Downloading
the new SPAM updates, support packages, and kernel patches
·
Preparing
the new SPAM updates, support packages, and kernel patches for application
·
Applying
the new SPAM updates, support packages, and kernel patches
·
Mass
recompiling all programs used in patched components
Be aware that SPAM/SAINT update and support package
application occurs within the SAP system using the SPAM transaction. These corrections are changes to ABAP program
code and must be handled in a special way by SAP. Kernel patches, on the other hand, are fixes
to SAP executables found on the SAP server.
Kernel patches must be applied when the SAP instance is down.
Please refer to the Check for New SPAM Updates, Support Packages and Kernel
To check if SAP has released any new software fixes
for your release of SAP, you need to know your current support package and
kernel release levels.
The patching process consists of:
-
finding
you current patch levels
-
finding
what patches you should be applying
-
downloading
the patches
-
unCARing
the patches
-
loading
the patches into the patching EPS queue
-
applying
the patches
Method One:
1. Log on to
your SAP instance, any client.
2. On any SAP
screen, click System -> Status…
3. On the System: Status popup, click the 
Component Information button.
4. On the System: Component Information popup, you
will see the support package
level for each component installed in your
current SAP instance.
Method Two:
1. Log on
your SAP instance, any client.
2. Go to
transaction SPAM.
3. On the Support Package Manager screen, turn
“on” the radion button beside
the Imported Support Packages in the Directory section of the screen, and
then click
Display button.
4. On the OCS Package Directory: Imported Packages
screen, you will see a list
of all SAP Support Packages imported into your
current SAP instance.
Method One:
1. Log on to
your SAP instance, any client.
2. Go to
transaction SM51.
3. On the SAP Servers screen, click on the server
for which you need the
information
and then click on the 
Release Notes button.
4. On the SAP Release Information from Server
screen, look down the SAP R/3
Kernel information section until you find Kernel Patch number. To the right,
you will find the current patch level of your
current SAP instance.
Method Two:
1. Log on to
the SAP instance sever using a Telnet session as user <sid>adm.
2. Change the
Telnet windows properties to use a Screen Buffer Size of 9999.
3. At the
Linux prompt, type:
disp+work –v
and press
ENTER.
4. Scroll
back up the listing to where you entered the command in step c.
5. Scroll
down the listing untill you find a line beginning patch number. To
the right
is the patch number for the SAP instance hosted on this server.
It should be
noted here that sometimes an older SAP may run on a newer SAP Basis level. For example, CRM 4.0 has a Basis level of a
6.20 instance but runs on a 6.40 kernel.
So make sure that the kernel patches you download match the SAP R/3 Kernel located via SM51.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new patches for CRM Basis expand as follows:
Support Packages and Patches
My
Company’s Application Components
SAP
CRM
SAP CRM 4.0
Entry by Component
CRM
Server
SAP
BASIS 6.20
3.
Scroll
down the Download screen until you
find your current package level. Any support
packages after your current level will need to be applied to your SAP System.
4.
You
may now leave the SAP Marketplace.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new patches for SPAM/SAINT for CRM 6.20 expand as
follows:
Support Packages and Patches
My
Company’s Application Components
SAP
SPAM/SAINT UPDATE
SPAM/SAINT
UPDATE 6.20
SPAM/SAINT
UPDATE 6.20
3.
Click
the Download tab of the SPAM/SAINT UPDATE screen. Find the SPAM/SAINT Update – Version XXX
value. If this SPAM version is higher
than you current SPAM version, you will need to download and apply the latest
SPAM update.
4.
You
may leave the SAP Marketplace.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new patches for CRM 4.0 expand as follows:
Support Packages and Patches
My
Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
ORACLE
& #Database independent
3.
Scroll
down the Download screen until under
the File Name column you find SAPEXEDB*.SAR files. Unless SAP has instructer you to use a
different kernel, the most recent SAPEXEDB*.SAR is the one you need to download. You may leave the SAP Marketplace.
4.
Now
go to the @Database independent section in the same list as ORACLE was
displayed. Scroll down the page until
you find the SAPEXE*.SAR that matches
the same number as the SAPEXEDB*.SAR
you found in the previous step. These
two files will give you a complete kernel replace.
5.
You
may leave the SAP Marketplace.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new patches for SPAM/SAINT for CRM 6.20 expand as
follows:
Support Packages and Patches
My
Company’s Application Components
SAP
SPAM/SAINT UPDATE
SPAM/SAINT
UPDATE 6.20
SPAM/SAINT
UPDATE 6.20
3.
To
download a SPAM/SAINT update, click on the SPAM/SAINT Update Title hyperlink. Click the Download
button. On the File Download popup, click the Save button. On the Save
As popup, select a location to store the SPAM/SAINT update and click the Save button. Alternatively, you may add the patch to your
SAP Download Manager and download all patches in one batch group.
4.
Once
you have downloaded your SPAM/SAINT updates, you may leave the SAP Marketplace.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new patches for CRM Basis expand as follows:
Support Packages and Patches
My
Company’s Application Components
SAP
CRM
SAP
CRM 4.0
Entry
by Component
CRM
Server
SAP
BASIS 6.20
3.
To
download a support package, click on the package Title hyperlink. Click the Download button. On the File
Download popup, click the Save button.
On the Save As popup, select a
location to store the support package and click the Save button. Alternatively,
you may add the patch to your SAP Download Manager and download all patches in
one batch group.
4.
Once
you have downloaded as many support packages as you need to apply, you may
leave the SAP Marketplace.
1.
Log
on to the SAP Marketplace using an OSS
ID with Administration rights – http://service.sap.com/patches.
2.
In
the navigator tree on the right-hand side of the My Application Components screen.
For example, to find new kernel patches for CRM 4.0 expand as follows:
Support Packages and Patches
My
Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
ORACLE
3.
To
download a kernel patch, click on the SAPEXEDB_<version>.SAR hyperlink. Click the Download
button. On the File Download popup, click the Save button. On the Save
As popup, select a location to store the kernel patch and click the Save button. Alternatively, you may add the patch to your
SAP Download Manager and download all patches in one batch group.
4.
Now
backup a step and instead of clicking ORACLE, click #Database independent. The full path would look like this:
Support Packages and Patches
My
Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
#Database
independent
5.
This
produces a list of database independent kernel patches. Scroll down the Download screen until under the File
Name column you find SAPEXE_<version>.SAR. Use the same instructions in step 5 to
download the patch. Make sure that the
version number of your database independent files matches the version number of
your MS SQL Server dependent file.
6.
Once
you have downloaded the kernel patch, you may leave the SAP Marketplace.
Unlike SPAM/SAINT updates, support
packages, and kernel patches, the storage location for other SAP binary patches
can be either SAP Marketplace or sapserv1.
SAP Marketplace is the normal respository but if you can’t find your
patch there, go look on sapserv1.
***Due to the shutdown of the sapserv1x
servers in April, this section has been discontinued. Everything should now to accessible via SAP
Marketplace.***
Prepare a
SPAM/SAINT Update or Support Package for Application
Once you have downloaded your SPAM/SAINT Update
and/or support package(s), they must be moved to the appropriate transport
directory and uncompressed.
1.
For
a SAP instance, move the downloaded K*.?AR file to the /usr/sap/trans/tmp
directory on the SAP Transport Domain Server which is normally the DEV server
of a SAP “Flavor”.
2.
Log
on to the appropriate server as <sid>adm.
3.
Type
the following:
cd /usr/sap/trans ¬
SAPCAR.EXE -xvf “tmp\*.?AR”
¬
This will unCAR all CAR and SAR files in the
\usr\sap\trans\tmp directory to the /usr/sap/trans/EPS/in.
4.
Log
off the server.
5.
Log
on client 000 of the appropriate SAP system.
6.
Go
to transaction SPAM.
7.
From
the menu bar of the Support Package
Manager screen, click Support Package
→ Load Packages → From application server.
8.
On
the SPAM: Confirm upload popup, click
the green √ picture-icon. The progress
of the support package loads will show in the status bar at the bottom of the
screen.
9.
Scroll
down the SPAM: Uploading Packages from
the file system screen to make sure your SPAM/SAINT update is listed. Use the Go Back icon to return to the
previous screen.
10.
You
may now leave the SPAM transaction.
Kernel patches must be applied on the SAP server. The SAP instance must be down before a kernel
patch can be applied.
1.
Logon
the server to be patched as <sid>adm.
2.
The
downloaded SAPEXE*.SAR and SAPEXEDB.SAR files must be uncompressed using
SAPCAR.EXE. You can place the
SAPEXE*.SAR files in any directory and use the SAPCAR.EXE –xvf “*.?AR” to unCAR
the files.
3.
You
may now leave the server.
Use the same procedure as Preparing a Kernel Patch for Application.
1. Log on to any client in the appropriate SAP system.
Device type = SWIN
Device Class = standard printer
Host spool access method = F: Printing on frontend computer Host printer = __DEFAULT. That is _ _ D E F A U L T
Domain. If the popup doesn't say that, press F6 to change to the
correct popup box.
Description, Name of DOMAIN_<SID>, and the description of the
Transport Domain. Then click Save.
installed SAP instances in your landscape yet, and assuming that you
want your transport requests to be transportable and not local only,
click on Overview → Systems.
\\<current server>:\usr\sap\trans for NT or /usr/sap/trans for UNIX. Click Environment → Transport Routes.
Domain. Press F6 until you see a TMS: Include System in
Transport Domain popup.
Description, Target Host, and System number of the TMS Domain
Controller then click Save.
included in the Transport Domain.
5. On the Enter Transport Request popup, click the Create Request icon.
6. On the Select Request Type popup, click "on" radio buttion Workbench Request.
7. On the Create Request popup, fill in the necessary information and make sure
Click the Save, OK, √ icon, etc. until everything is done. You will
6. Back on the Change Transport Routes screen, click on the QAS instance and
FROM AGR_TEXTS, AGR_TCODES, TSTCT
WHERE AGR_TEXTS.MANDT = '000' AND
AGR_TEXTS.SPRAS = 'E' AND
AGR_TEXTS.LINE = 0 AND
AGR_TCODES.MANDT = '000' AND
AGR_TCODES.AGR_NAME = AGR_TEXTS.AGR_NAME AND
TSTCT.SPRSL = 'E' AND
TSTCT.TCODE = AGR_TCODES.TCODE
ORDER BY AGR_TEXTS.AGR_NAME, AGR_TCODES.TCODE;
2. Try End session through SM50 or cancel program from SM66.
3. If the Work Process in SM50 is in stopped state then killing it will not help much or quickly, you need to identify why it is stopped (running a program on another server, runing in parallel etc.) Try and end those.
4. Kill Work Process in SM50 without core.
5. Kill process or PID via program RSBDCOS0.
6. If all else fails, restart the SAP instance server.
The most important things to remember when killing a WP are:
1. Change to restart = no as otherwise the session can jump back in sometimes as most of its memory is not actually living in the WP.
2. Allow it a long time to stop, there is no need to do it twice or 50 times as I have seen some people do, the poor old thing is just trying to recover rollback and reinitialize itself.
Component Information button. Display button. Release Notes button.Before you apply the most current SPAM/SAINT, please pull the OSS Note 484219 - Known problems with transaction SAINT in Basis Release 6.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch.
Once you have loaded the latest SPAM/SAINT update
into your support Package manager buffer, you need to apply the update to your
SAP system.
1.
Log
on client 000 of the appropriate SAP system.
2.
Go
to the SPAM transaction.
3.
From
the menu bar of the Support Package
Manager screen, click Support Package
→ Import SPAM/SAINT update. Click the green √ picture-icon to continue.
4.
The
progress of the SPAM/SAINT update application will be displayed in the status
bar at the bottom of the screen. These
messages look very similar to the messages generated during a change request
transport.
5.
When
the Restart SPAM popup appears, click
the green √ picture-icon to leave the SPAM transaction.
6.
Go
to the SPAM transaction. You may notice
programs compiling in the status bar at the bottom of the screen. This is normal.
7.
Once
you are again on the Support Package
Manager screen, verify that the SPAM
status in the Status section of
the screen contains a green light.
8.
You
may now leave the SPAM transaction.
Before applying any support packages to your SAP system, release all “repair” change requests to prevent error messages due to locked resources. Repairs are usually advanced corrections obtained from SAP Notes that are eventually accumulated into support packages. So the same objects “repaired” in the advanced corrections will be “repaired” during the application of the support package. Releasing the repair change requests allows the support package to overlay the temporary advanced correction “fix”.
Before you apply the most current SPAM/SAINT, please pull the OSS Note 782140 - OCS: Known problems with Support Packages in Basis Rel.6.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch.
Once you have loaded the latest support
packages into your support
Package
manager buffer, you need to apply the packages to your SAP
system.
1.
Log
on client 000 of the appropriate SAP system using a adminitrator user ID that
is not DDIC or SAP*.
2.
Go
to the SPAM transaction.
3.
On
the Support Package Manager screen,
click the Display/Define button to
build your import queue. On the Component Selection popup, click on
the Comp. ID having support packages you want to install. The component order support packages should
be applied is SAP_BASIS, SAP_ABA, SAP_APPL, and PI.
4.
A
list of all application support packages for the selected component will appear
in the Define Queue popup. Select the support packages you want to
apply. See SAP Note 782140 for information
on restrictions to grouping support packages into queues. The Package ID with the green √ to the left
is the highest support package to be placed in the queue. All lower number support packages for this
component will be applied as well. Click
the green √ picture-icon to confirm the queue.
5.
From
the menu bar of the Support Package
Manager screen, click Support Package
→ Import queue.
6.
On
the SPAM: Import Queue popup, read
the displayed information and then click the green √ picture-icon to continue.
7.
The
progress of the support package application will be displayed in the status bar
at the bottom of the screen. These
messages look very similar to the messages generated during a change request
transport.
8.
When
the Imported successfully Information
popup displays, click the green √ picture-icon to continue.
9.
On
the Support Package Manager screen,
verify that the SPAM status in the Status section of the screen contains a
yellow light and the Next action
value is Confirm queue. To confirm that your support packages applied
completely, click the green √ picture-icon.
A Support Package queue was
confirmed message will appear in the status bar at the bottom of the
screen.
10.
You
are ready to build another support package queue, or if you have applied all
the necessary support packages, you may now leave the SPAM transaction.
*** It is recommended that
the /usr/sap/<SID>/SYS/exe/run directory be copied to
/usr/sap/<SID>/SYS/exe/backup_run before replacing the kernel ***
1.
Log
on to the appropriate server as <sid>adm.
2.
Double
check that the SAP instance, SAPOSCOL, and SAP<SID>_00 services are
stopped.
3.
To
apply the new kernel patch to a R/3 instance, copy the new files into usr\sap\<SID>\SYS\exe\run
directory. If prompted for overwrites,
say yes to all.
4.
After
the new kernel has been copied make sure that the following file ownerships are
correct:
All files in /usr/sap/<SID>/SYS/exe/run <sid>adm
/usr/sap/<SID>/SYS/exe/run/saposcol root
/usr/sap/<SID>/SYS/exe/run/br* ora<sid>
/usr/sap/<SID>/SYS/exe/run/sapdba ora<sid>
5.
After
the successful completion of the kernel patch, you may bring the instance back
up and log off the server.
Use the same procedure as Application of SAP Kernel Patches.
Other SAP Issues
1.
What
has changed since the performance is poor?
- System Parameter
Changes (RZ10)?
- Increase in the
number of users?
- Kernel patch?
- Support Packages?
- Linux and Oracle
patches?
- Hardware Changes?
2.
Any
signs of general problems in the System Log - SM21?
3.
Places
to look:
- SM50: → Process → Trace → Components – is there a
Trace level set? Is it greater than 1? What is the utilization of the work
processes? Click the white clock
picture-icon. Is the total CPU
for the last dialog process > 10 minutes?
- ST04: Is the database monitor activated? If yes,
it should deactivated it in normal operation. ST02:
Check the buffering quality. If
paging occurs in a buffer, the corresponding parameter should be
increased. Also refer to SAP Note 121625 in this context.
- ST03: → Select a server → Today's Workload: What are the response times? In the
case of poor response times, where is most of the time needed? Button
'Top Time': Are there a lot of
different transactions with poor response times or are there only a few?
Is a certain transaction always slow or only sometimes?
- ST06: → Detail analysis menu → Hardware
Info. To which extent are the
hardware resources utilized? Call
ST06 at times with poor
system performance. What is the
CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes
and display the main CPU consumers.
What is the utilization of the disks? How high is the paging in the base
pool?
4. If only few transactions are
affected by the performance problem, you should additionally note the following
points:
1.
Check
whether modifications were made in the affected or related transactions.
2.
ST03: Display the corresponding
performance records.
3.
SE30: Carry out a runtime
analysis for the affected transactions.
4.
ST05: If the database times are
high, you should generate an SQL trace of the affected transactions to find out
whether the database access is carried out in a useful way.
5. Look for
tables that have experienced unusual monthly growth.
1.
DB02 → Space Statistics button
2.
Press
Enter on the Tables and Indexes popup
3.
History → All objects off/on
4.
Click
the Months button
5.
Click
on the first number under the Rows –
Chg/Month header and click the Sort
button.
6.
The
sorted results shows the top tables when it comes to rows changes per
month. These tables are your “database
hogs”.
6. What is
considered “normal” response time?
Performance
Standards:
Response time -- 1 second (dialog), < 1 second (update)
CPU time
-- approx 40% of average response time
Wait time -- < 1% of average response time
Load time -- < 10% of average response time
DB request time -- approx
40% of average response time
Database Standards:
Direct reads -- < 10 ms
Sequential reads-- < 40
ms
Changes -- < 25 ms
High Value Indications:
DB request time –- Database
or index problems
Load time -- Buffer problems
Wait time -- Not enough work processes
Locked
tasks
Long
running transactions
Whether you are trying to start a brand new SAP
instance, or an old one, there are some very specific places to look for
information.
If this is a brand new SAP instance, and the
installation completed 100% successfully, you know that the instance itself
must be viable. If your installaion was
never able to complete due to the instance not being able to start up, the
issue is probably due to lack of resources.
Use the sapinst directory to search the installation logs and find your
problem. Sort them with “ls – ltr” is
see the list sorted in descending order for the ease of viewing.
If you have a test searching tool, look for “error”
in all files with the suffix “.log”.
If your SAP instance has been up and running fine
for a good while, then something has probably changed that makes it not come
up.
·
have
you changed any instance paramters?
·
did
you do a kernel replacement for some reason?
·
have
there been SAP Support Packages applied that might
necessitate
a kernel replacement?
·
have
there been OS patches?
·
is
the database archiver stuck or hosed?
·
has
a crucial directory run out of space?
·
has
a semaphore or ipc segment gotten stuck from a previous run?
·
is
your memory so fragmented that it can’t get enough primary space to start the
instance?
·
has
someone changes the directory privileges?
To investigate an unsuccessful start up, look at the
logs in the /home/<sid>adm directory.
Sort them with “ls – ltr” is see the list sorted in descending order for
the ease of viewing.
If nothing obvious is found, go to the
/usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this
directory. The most useful information
can be found in the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files.
If all else fails, zip the contains of the
/usr/sap/<SID>/DVEBMGS00/work directory, open a problem with SAP, and
attach the zipped file to it. Also
provide them with the answers to the above questions as well as your current
hardware and database platforms, patch level for SAP support packages, kernel,
and the OS, and anything else you might think useful.
The Delicate Art of SAP Note Search
How often have you seen a posted message saying
"I have searched through SAP Notes and can find nothing related to this
matter."? And how often have you gone to SAP Marketplace and done a search
yourself and found a hit? If we only had a had a nickle...
Searching SAP Notes (formerly known as OSS
notes) is a science as well as an art. Lets use this error message as an
example:
"BR051I
BRBACKUP 6.10 (80)
BR055I Start of database backup:
bdmsqjbi.anf 2004-02-27 00.05.42
BR602W No valid SAP license found -
please contact SAP"
First, you should search the specific error message "BR602W No valid SAP
license found". If you get at least one hit, you should read the SAP Note
even if it didn't look as if it pertained 100%. Why? Because
it might contain information leading to other notes that did pertain, or give
you new ideas for more search terms to help narrow the scope of my query.
If you didn't find a note that matched the problem, you could make your next
search a little less specifc, like "brbackup No valid SAP license
found". First you could search for the phrase, and if you had no luck, you
could search for all words. And if that produced nothing tangible, you could
make it even less specific as in "brbackup SAP license error" or
"SAP license error".
Normally a very specific query will get you the results you need. But sometimes
things get lost in translation. For example, you are applying support packages
and get an import error with the following message "Panic! Panic! Panic!
there's no object header". Since we speak English and we realize that the
SAP product was designed and implemented in Germany, we have to guess that the
English word "Panic!" somehow was translated from the German word
"Warning!" and that we can temporarily delay a panick attack until we
can research the error. Moral of the story? Realize that some things just don't translate
correctly from language to language, and search accordingly. If you searched
for "Panic! Panic! Panic!" and got no hits, you could try
"warning message no object header".
Last, and not least, read and become familiar with your SAP Notes. There are
certain notes that you pull over and over again due to some task that needs
fresh, current and precise information. These are mostly lists of supported
printer devices, known problems with applying patches, etc.
If a user seems to be experiencing SAPGui errors,
several things need to be checked:
·
Is
the operating system on the user’s workstation patched to the level recommended
by SAP?
·
Is
the user using a version of SAPGui that is too old for his workstation?
·
Is
the user using a version of SAPGui that is not certified for his operating
system?
·
Is
the user’s workstation having resource problems?
·
Is
the user’s workstation connected to the LAN?
·
Can
a different user reproduce the same error on the same workstation?
·
Are
there any SAPGui patches that have not been applied?
Most SAPGui problems can be solved by either a)
deleting and reinstalling SAPGui on the workstation, or b) deleting and
installing a newer version of SAPGui.
Make sure that these lines were added to the
services file on the user’s workstation:
After you have successfully configured your SAPGui,
add these three lines to the bottom of your
\Windows\system32\drivers\etc\services file:
sapdp00 3200/tcp
sapmsR3I
3600/tcp
#
If you have SAP Instances using System Numbers other
than 00, you will have to add their equivalents to the services file as
well. Also, check if you are having
connection problems due to firewall restrictions. And, be sure that your Insert Key is set so
that you can type your password in properly – you can delete whatever is in the
password field in order to enter your password.
If you have never tested connectivity to a SAP
instance on the workstation having the connection problem, first you need to
make sure that the workstation can connect to the SAP server in some non-SAPGui
way. Let’s say your user us trying to
connect to System ID (SID) DEV, System Number 00, and IP address
10.1.10.11. Open a DOS-Windows and type
this:
telnet 10.1.10.11 3200¬
If the screen
rolls and goes totally blank then your dispatcher is reachable. You can close
the DOS session. If your window never goes completely blank and you set a
"Connecting To 10.1.10.11... Could not open connection to the host, on
port 3200: Connect failed" error message right under the command you
entered, the dispatcher is not reachable. Also, make sure the \Windows\system32\drivers\etc\hosts
file on the workstation is correct.
For information regarding operating system,
resource, and hardware requirements for running SAPGui, see SAP Note 26417 - SAP GUI Resources: Hardware and software.
Central User
Administration is Not Transferring Change from the CUA Parent
Client
If CUA stops sending changes from DEV to QAS or PRD,
something in the RFC setup has changed.
Either the password or the user type for RFC_USER was changed, or the
SM59 RFC connection to was changed and is no longer working.
Use SCUL in DEV in your DEV CUA parent to list the
errors that are occurring. Look for the
user you tried to transport but could not.
You might see “You are not authorized to change users in group” or “No
authorization for group users in role”.
This does not mean that YOU are not authorized, it means that the
RFC_USER doing the ALE communication between the SAP systems is not authorized.
First, reset the RFC_USER password in DEV, QAS, and
PRD. And make sure that the user type is
Communication and not dialog. Now go to
sm59 and do remote logins using the QAS RFC connections. If they work (ie nothing seems to happen
after you click the remote logon button) everything should now be fixed. If you get a logon screen for QAS, change the
password in the sm59 screen to the same password you changed RFC_USER to in DEV
and QAS.
Retry your user change. If it still doesn’t go to QAS, maybe the QAS system
is hosed and down.
Important SAP Marketplace Links
Inbox http://service.sap.com/inbox Read messages from SAP to you
Installation Guides http://service.sap.com/instguides Download SAP product installation
guides
License Keys http://service.sap.com/licensekey Request New Permanent License Key
Messages to SAP http://service.sap.com/message Open problems with SAP
QuickLinks Page http://service.sap.com/quicklinks An index of SAP links
Oracle DBA Page http://service.sap.com/dbaora Page for Oracle DBA Material
OSS Notes http://service.sap.com/notes Search the SAP Notes Database
Patches http://service.sap.com/patches Download SAP software patches
Remote Connection http://service.sap.com/remoteconnection Learn about the OSS connection and
order
it from SAP
Service Connection http://service.sap.com/serviceconnection Open a Service Connection for SAP
to
access your SAP landscape
Installation CDs & DVDs
SSCR http://service.sap.com/sscr Register
Developers and Changes
made
against SAP objects
User Administration http://service.sap.com/user-admin Add/Change OSS ID user information
- System Parameter Changes (RZ10)?
- Increase in the number of users?
- Kernel patch?
- Support Packages?
- Linux and Oracle patches?
- Hardware Changes?
- SM50: → Process → Trace → Components – is there a Trace level set? Is it greater than 1? What is the utilization of the work processes? Click the white clock picture-icon. Is the total CPU for the last dialog process > 10 minutes?
- ST04: Is the database monitor activated? If yes, it should deactivated it in normal operation. ST02: Check the buffering quality. If paging occurs in a buffer, the corresponding parameter should be increased. Also refer to SAP Note 121625 in this context.
- ST03: → Select a server → Today's Workload: What are the response times? In the case of poor response times, where is most of the time needed? Button 'Top Time': Are there a lot of different transactions with poor response times or are there only a few? Is a certain transaction always slow or only sometimes?
- ST06: → Detail analysis menu → Hardware Info. To which extent are the hardware resources utilized? Call ST06 at times with poor system performance. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. What is the utilization of the disks? How high is the paging in the base pool?
Searching SAP Notes (formerly known as OSS notes) is a science as well as an art. Lets use this error message as an example:
"BR051I BRBACKUP 6.10 (80)
BR055I Start of database backup: bdmsqjbi.anf 2004-02-27 00.05.42
BR602W No valid SAP license found - please contact SAP"
First, you should search the specific error message "BR602W No valid SAP license found". If you get at least one hit, you should read the SAP Note even if it didn't look as if it pertained 100%. Why? Because it might contain information leading to other notes that did pertain, or give you new ideas for more search terms to help narrow the scope of my query.
If you didn't find a note that matched the problem, you could make your next search a little less specifc, like "brbackup No valid SAP license found". First you could search for the phrase, and if you had no luck, you could search for all words. And if that produced nothing tangible, you could make it even less specific as in "brbackup SAP license error" or "SAP license error".
Normally a very specific query will get you the results you need. But sometimes things get lost in translation. For example, you are applying support packages and get an import error with the following message "Panic! Panic! Panic! there's no object header". Since we speak English and we realize that the SAP product was designed and implemented in Germany, we have to guess that the English word "Panic!" somehow was translated from the German word "Warning!" and that we can temporarily delay a panick attack until we can research the error. Moral of the story? Realize that some things just don't translate correctly from language to language, and search accordingly. If you searched for "Panic! Panic! Panic!" and got no hits, you could try "warning message no object header".
Last, and not least, read and become familiar with your SAP Notes. There are certain notes that you pull over and over again due to some task that needs fresh, current and precise information. These are mostly lists of supported printer devices, known problems with applying patches, etc.
If the screen rolls and goes totally blank then your dispatcher is reachable. You can close the DOS session. If your window never goes completely blank and you set a "Connecting To 10.1.10.11... Could not open connection to the host, on port 3200: Connect failed" error message right under the command you entered, the dispatcher is not reachable. Also, make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct.
Comments
Post a Comment