10/11/12 BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials 1/27 https:// sites.google.com/site/saparchives/ SAP-ba sis-oper ation-1 ---w indow s SAP BASIS Administration and Learning Tutorials Welcome to BASIS World !!! U can send BASIS content to jus [email protected]and will add it to SAPArchives. SAP BASIS Tutorial 1 - Windows SAP BASIS Material SAP BASIS BASIS FAQs BASIS Transactions SAP BASIS Scope SAP Forum Starting the SAP Instance The normal SAP instance start up consists of three parts: starting the SAP OS Collector, starting the Oracle Listener, and starting the SAP instance. TheSAP OS Collector (saposcol) and the Oracle Listener (Oracle<SID>TNSListener) are registered as Services on yourhost server during installation so you should not normally need to start either of these programs. There is also Services called SAP<SID>_<system#> and which must be started. Even if you have multiple SAP instances on a server, the start up process is pretty much the same. If you have only one SAP instance on ther server, you will have one saposcol and one Oracle<SID>TNSListener running as Services. If you have two SAP instances on the same server, you will have one saposcol and two Oracle<SID>TNSListeners unless you the database for the second instance was installed as a MCOD or you made major changes to listener.ora and tnsnames.ora files, either case which allows you to share one listener for multiple instances. If you have multiple listeners due to multiple SAP instances, remember that the key to having all your SAP instances happy with Oracle is to have each Oracle instance use a different listener port. The default Oracle is port 1521 during the Oracle database instance Search this site
27
Embed
SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
Daily backups should be made for these MS SQL Server specificdirectories:
All \>SID>Datax directories
All \>SID>Logx directories
Weekly backup should be made for these OS specific directories:
The c: drive
The registry The hard disk mapping For Oracle, the entire \oracle directory should be backed up dailyif there is only one Oracle Instance on the server, and eachseparate \oracle\<SID> directory if there is more than oneinstance on the server. If MS SQL Server, the data and log filesmust be backed up. 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 specificdirectories:
\usr\sap\<SID>
Any directories containing flat files that are used by the SAPinstance Weekly backups should be made for these Oracle specificdirectories:
\oracle\<SID> Directory holding redo logs if not in the \oracle structure Weekly backups should be made for these MS SQL Server specific directories:
All \>SID>Datax directories All \>SID>Logx directories Monthly backup should be made for these OS specific directories:
The c: drive
The registry The hard disk mapping For Oracle, the entire \oracle\<SID> directory should be backedup daily if there is only one Oracle Instance on the server, andeach separate \oracle\<SID> directory if there is more than oneinstance on the server. If MS SQL Server, the data and log filesmust be backed up. It is also recommended that a full offline image of the entire server be made at the same time every month.
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
1. Log on to the appropriate server as <sid>adm.2. Click Start → Administrative Tools → Services toopen a Services window.
3. Right-click on the SAPROUTER service and clickStart .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 toopen a Services window.3. Look at the SAPROUTER service. If is notstarted, right-click to start the service. If it is started, right-
click & Stop the service and then right-click & Start theservice. This should “bounce” your saprouter instance.4. You may now log off the server.
Stopping saprouter
1. Log on to the appropriate server as <sid>adm.2. Click Start → Administrative Tools → Services toopen a Services window.3. Right-click on the SAPROUTER service and click
Stop.4. You may now log off the server.
Applying a SAP Note
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
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
1. Log on to client 000 in the appropriate SAPsystem.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 boxand click the clock picture-icon. A SAP Note XXXXXX is
being downloaded message will appear in the bottomstatus 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 willappear on the Assistant - Version XXX\XXXX: Worklist
screen under the SAP Notes → New navigation tree. TheSAP Note can only be applied if there is a blue box with ablack arrow to the left of the note number. If there is a graydiamond 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 thedownloaded SAP Note number.7. On the Note Assistant – Display Note XXXXXX
screen, read the note text to see if there are any necessarymanual tasks to be performed after the note is applied.When you are ready to apply the note, click on the clockpicture-icon.8. If there are any prerequisite SAP Notes which
need to be applied to the SAP system before thedownloaded SAP Note can be applied, a list will appear in aLoad the following notes into your SAP system popup willappear. Click the clock picture-icon to download theseprerequisite SAP Notes as well. If any of the prerequisiteSAP Notes must be applied in parallel with the originaldownloaded SAP Note, a list will appear in a SAP Note
queue to be Imported popup. Click the clock picture-iconto apply all the listed SAP Notes.9. Before applying any SAP Notes to your SAPsystem, a Confirmation: SAP Note read popup will appear.Once you have read the information contained in this
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
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 anew change request. On the Create Request popup, fill inthe Short description and click the Save picture-icon. Youwill 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 SAPsystem, you will be returned to the Note Assistant -
Version XXX\XXXX: Worklist screen. There is nocompletion 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 radiobutton. Click the green √. You can now leave theSNOTE
transaction. Modified programs, functions, etc. may requirerecompilation.15. If the OSS note you applied changed a ABAPprogram, you must go to the SE38 transaction andmanually 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 canback out of the SE37 transaction.
Working with the SAP Marketplace
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’treceive this e-mail promptly, it is important
to know how to obtain the newly generated key
“the old-fashioned way”.
Finding your Hardware Key
1. Log on to the server containing the new SAPsystem as <sid>adm.2. Open a DOS-prompt window and type thefollowing, pressing enter when you are done:
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
3. You will see a line reading “saplicense:HARDWARE KEY = XXXXXXXXXXXXXX”. Make note of thisinformation before pressing Enter.4. You may now close the DOS-prompt window andlog off the server.
Alternative Method for Finding your
Hardware Key
1. Log on to client 000 of the newly installed SAPsystem.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. Thehardware key will appear in the box to the right of theDetrmne 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 IDwith Administration rights –
http:\\service.sap.com\licensekey.2. In the navigator tree on the right-hand side of theLicense 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 thecorrect Installation hyperlink the mySAP Business Suitecomponent.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 youhave supplied the hardware key, click the Save New Item
button. The license key request will be shifted up to thefirst line of the License request list. Click on the □ to theleft of the license request to place a √ in the box. Now youare 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 IDwith Administration rights –http:\\service.sap.com\licensekey.2. In the navigator tree on the right-hand side of theLicense 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> youprovided during the request process. If the Status showsas Sent to SAP , the license key has not yet beengenerated. If the Status shows as Completed , your newlicense key has been generated and you can click on the<SID> System hyperlink to continue.5. On the License key: request screen, scroll downuntil you can see the License request section. Under the
License key header you will see you new SAP systemlicense key. Write this key down and remember that it iscase sensitive. Or you can cut-and-paste it to a moreconvenient 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 SAPsystem as <sid>adm.
2. Open a DOS-prompt and type: saplicense -install ¬
3. You will be prompted for the <SID>, hardwarekey, expiration date of the new license, and the newlicense. Press Enter after the entry of each piece of data.4. Once the new license key has been accepted,you will received a License key applied message. If youhave the TXT file SAP e-mailed you, you can place itsomewhere on your server and use the following syntax toinstall the license as well:
saplicense –install ifile=<location of TXT file>¬
4. You may now log off the server.
Applying a SAP License Key the New Way
1. Log on to client 000 in the SAP system in whichthe new license key is to be installed.
2. Go to transbaction 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 newlicense key you obtained from SAP. Click network picture-icon to finish the new license installation.5. You will receive a License k ey successfully
installed message. You may now leave the SLICENSE
transaction.
Generating a Developer’s Key for a
Programmer
1. Log on to the SAP Marketplace using an OSS IDwith Administration rights – http:\\service.sap.com\sscr .2. In the navigator tree on the right-hand side of theSSCR screen, click on Registration.3. On the SSCR – Registration screen, click the
Register developer radio button and click an Installationhyperlink. Make sure you select the correct InstallationNumber for the SAP “flavor” you need or the generated keywill not work.4. On the SSCR – Register Developer screen, typein the developer’s SAP user ID and click the Register
button.5. A new Details section will appear. Note thegenerated developer’s key or cut-and-paste for other storage.6. You may now close your web browser session.
Generating an Object Key to Change a
SAP-owned Object
1. Log on to the SAP Marketplace using an OSS IDwith Administration rights – http:\\service.sap.com\sscr .2. In the navigator tree on the right-hand side of theSSCR screen, click on Registration.3. On the SSCR – Registration screen, click theRegister object radio button and click an Installation
hyperlink. Make sure you use the MS SQL installation andnot R/3.4. On the SSCR – Register Object screen, fill in theinformation necessary to generate an object key. If youneed 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 theSAP Note containing the advanced correction. Click theRegister button once all information has been enter.5. A new Details section will appear. Note thegenerated object key or cut-and-paste for other storage.6. You may now close your web browser session.
a Security Audit Trace has been activated forthe 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 theService Connections button.3. On the Service Connections – Overview screen,scroll down the page and find the SAP instance you wantto open. Click on the red X in that instance’s line.4. In the Enter Data for the system’s semi-automaticopening popup, set the days, hours, and minutes you wantthe 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 OSSID with Administration rights –
http:\\service.sap.com\message.
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 SAPsystems registered with SAP. From the expanded list of system, click on the radio button just left of the <SID> forwhich 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 theSystem 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 theproblem 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 thatthe information showing in the Oper. System, Database,and Frontend dropdowns is correct. If it is not correct,selection your SAP system’s information from theappropriate dropdowns. Click the Continue hyperlink.7. On the next Customer messages – Create
screen, scroll down to the bottom of the screen. Fromthe Priority dropdown, select the appropriate priority of Low , Medium, High, or Very High. From the Component
dropdown, select which SAP component is having theproblem. Once you select a component, a secondaryComponent dropdown will appear. Select a secondary
component and a third component as well. Do the bestyou 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 alanguage from the Language dropdown, type a short butdescriptive 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 assistSAP 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 tothe 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 aspossible, click the Send to SAP hyperlink.11. You will receive a confirmation screen with ageneration problem number. Write this problem number down for later use.12. You may now leave the Message Wizard andclose 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 –
http:\\service.sap.com\message.2. Click on Customer Messages. All the open OSS problemsyou have sent to SAP will appear here.
3. You may now leave the Message Wizard and close the webbrowser window.
Creating, Modifying, Deleting, Transporting, and
Resetting Print Devices
Creating a Print Device
1. Log on to any client in the appropriate SAPsystem.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 intochange mode. The easiest way to create a new printer isto copy an existing one. Click on a similar printer in theoutput devices screen then click the create with templatepicture-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 onthe Device Attributes and Host Spool Acc Method tabs.When all the required data has been changed\added, clickthe 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.
Modifying a Print Device
1. Log on to any client in the appropriate SAPsystem.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 intochange mode. Double click on the output device to bechanged.5. On the Spool Administration: Output Device
(Change) screen, make any necessary changes on theDevice Attributes and Host Spool Acc Method tabs. Whenall the required data has been changed\added, click theSave 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/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
1. Log on to any client in the appropriate SAPsystem.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 intochange mode. Click on the output device to be deleted andthen click the trash can picture-icon.5. On the Spool admin.: Delete screen, verify thatthe correct printer is about to be deleted. Click theYes
button.6. You will receive an Output device deleted
message in the status bar at the bottom of the screen. Youmay now leave the SPAD transaction.
Transporting a Printer or a Group of Printers
1. Log on to any client in the appropriate SAPsystem.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 intochange mode.5. Click on an output device to be transported andthen 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 changerequest. On the Create Request popup, fill in the Short
description and click the Save picture-icon. You will bereturned to the Prompt for transportable Workbench
request popup which contains the generated changerequest 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 thescreen. Repeat steps 11 through 14 as many times asnecessary, using the same transport request for allprinters.9. You may now leave the SPAD transaction.
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
1. Log on to any client in the appropriate SAPsystem.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 toreset.5. On the Spool Administration: Output Device
(Display ) screen, click on the pencil picture-icon to switchfrom 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.
Printer Output
Creating a Local aka Frontend Printer
aka Desktop Printer
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 toprint 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.
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
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, fillin 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 = SWINDevice Class = standard printer
And the following Access Method fields:
Host spool access method = F: Printing on frontendcomputer Host printer = __DEFAULT. That is _ _ D EF 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 usethe default printer of the current workstation.
Viewing a List of Pending Printer
Output Requests for All Printers
1. Log on to any client in the appropriate SAPsystem.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 tofilter the selection results. Then click on the clock picture-icon.5. A lis t of all pending output requests will bedisplayed.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 SAPsystem.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
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
to check the output requests. Then click on the printer andpage picture-icon.4. A lis t of all pending output requests for theselected printer will be displayed.5. You may now leave the SPAD transaction.
Reprinting a Document
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction SP01.3. On the Output Controller: Spool request selection
Screen screen, fill in any information needed to filter theselection results. Then click on the clock picture-icon.4. A lis t 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 bottomstatus bar.6. You may now leave the SP01 transaction.
Re-routing Print to a Different
Printer
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction SP01.3. On the Output Controller: Spool request selection
Screen screen, fill in any information needed to filter theselection results. Then click on the clock picture-icon.4. A lis t 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 andselect 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, clickthe Yes button. An Output request created messageshould appear in the bottom status bar.8. You may now leave the SP01 transaction.
Deleting Obsolete Temporary Objects and
Reclaiming the Space
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction SP12.
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
Sequential Data screen, on the top-most menu bar clickTemSe 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 inthe Days box with “7” for development and qualityassurances SAP systems, and “32” in production SAPsystems. 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 selectedtemporary 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.
Mass Recompilation of ABAP Programs
1. Log on to any client in the appropriate SAPsystem.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 radiobutton to the left. Click on theContinue button at thebottom.4. On the SAP Load Generator screen - Selection by
software components of generation set section, click thebutton to the left of each entry listed in theSoftware
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 beone entry in the Server box. Click the button to the left of this entry. Click the Continue button at the bottom of thescreen. Several messages will appear in the bottom statusbar 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 onthe Schedule job at button.
7. On the SAP Load Generator – Job Monitor screen – Load generator status section, the status of massgeneration is shown. You may now leave the SGEN
transaction and later return to check the progress of therecompilat ion. No other load regeneration jobs can bescheduled 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.
SAP IGS Server
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
service can be done using the Services sessionon the SAP server.
The most current installations of SAP use the
START profile of the SAP instance to start the
IGS server and it appears as a process in the
Process List of the SAP MMC Console.
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,
can take 15 minutes, or several days. As you
work with the
various SAP provided tools, you will learn the
difference between
normal lag time, and the possibility ofsomething being “wrong”.
Requesting A New SAP Marketplace User ID aka “S” Number aka
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 addedas these are all required fields.2. Log on to the SAP Marketplace using an OSS IDwith 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 thegathered information from step #1. Then press Save. Youmay 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 IDwith 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 willsee 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 rowto performa a search.4. Verify the status of the OSS ID for which you arelooking. 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 theinformation on to your user.
If the Status reads “Requesting…”, your OSS ID has notbeen 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. Thenormal turnaround for an OSS ID generation is eight hoursor 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 IDwith 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 beasked for your OSS ID and password again, dependentlyon your point of original logon.3. On the User Data Maintenance screen, clickSearch 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, clickon 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 youwant to change. For example, if you want the OSS ID tobe able to create new OSS problems with SAP, click theCreate Customer messages “on” box at the far left to theline.7. On the resulting User Data Maintenance CreateCustomer messages screen, click “on” your option –
Customer if you want the user to be able to open problemsfor any SAP Instance you own, or select a specificInstallation(s) for only, say, CRM instances.8. Click the Add button at the bottom of th page, andyou will be returned to step #6. Repeat as many times asyou 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 andclick Save. You should get a screen thanking you andsaying that your changes have been saved.10. You may now log off the SAP Marketplace.
Creating, Modifying, and Deleting System
Parameters
Creating System Parameters
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction RZ10.
3. On the Edit Profiles screen, select the<SID>_DVEBMGS00_SAP<SID> Profile from thedropdown, or whatever instance profile you need tochange. In the Edit profile section, click the radio button tothe left of Extended maintenance. Click the Change button.4. On the Maintain R/3 Profile screen, click the Add
Parameter button.5. On the next Maintain R/3 Profile screen, type inthe new Parameter name and Parameter val . Click theCopy button. Click the white arrow on green picture-icontwice.6. On the Maintain R/3 Profile popup, click the Yes
button to save your changes.7. On the Edit Profiles screen, click the Savepicture-icon.8. On the Save profile popup, click the No button.9. On the Activate profile popup, click the Yes
button.10. On the Edit Profiles popup, click the green √button.11. On the Caution! Caution! Caution! popup, click thegreen √ button.12. If you receive a Possible Inconsistencies in OPModes screen, double click over the <No> unless you are
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
unsure of why this message has been displayed.13. You will not get a confirmation message. You maynow leave the RZ10 transaction.
Modifying System Parameters
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 thedropdown, or whatever instance profile you need tochange. In the Edit profile section, click the radio button tothe left of Extended maintenance. Click the Change button.4. On the Maintain R/3 Profile screen, locate theparameter that needs to be changed in theParameter
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 Savepicture-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, clickthe green √ button.10. If you receive a Possible Inconsistencies in OPModes 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 maynow leave the RZ10 transaction.
Deleting System Parameters
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction RZ10.3. On the Edit Profiles screen, select the
<SID>_DVEBMGS00_SAP<SID> Profile from thedropdown, or whatever instance profile you need tochange. In the Edit profile section, click the radio button tothe left of Extended maintenance. Click the Change button.4. On the Maintain R/3 Profile screen, locate theparameter you need to delete and click on the Parameter
name to high-bright it. On the top-most menu bar, clickParameter → Delete.5. On the next Maintain R/3 Profile popup, makesure that the parameter listed is the one you need todelete. Click the Yes button to delete the parameter. Youwill receive a Parameter was deleted message in the status
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
bar at the bottom of the screen. Click theCopy button.Click the white arrow on green picture-icon.6. On the Edit Profiles screen, click the Savepicture-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 thegreen √ button.11. If you receive a Possible Inconsistencies in OPModes screen, double click over the <No> unless you areunsure of why this message has been displayed.12. You may now leave the RZ10 transaction.
Overview of All Work Processes Running on a SAP
System
1. Log on to any client in the appropriate SAPsystem.2. Go to transaction SM50.3. On the Process Overview screen, all processingthreads for the SAP system are displayed. If a thread isbeing used, the name of the report running will be displayedas well as the number of seconds that the report has beenrunning, the client in which the report is running, the actionthe report is currently doing, and, if applicable, the table thereport 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 theamount of CPU time consumed by each process thread sofar.6. Double click any display line containing a reportname in order to see more detailed information about therunning report. This information includes database accessstatistics and timings. Use the white arrow on greenpicture-icon to go back to the Process Overview screen.7. Click on any process thread and then click theblue cylinder with glasses picture-icon. This will displaythe Trace Data screen which shows the actual
communication between SAP, the operating system, andthe database server. This information is useful whentracking process thread problems. Use the white arrow ongreen picture-icon to go back to the Process Overview
screen.8. You may now leave the SM50 transaction.
Stopping Run-Away or “Bad” Work Processes
1. Log on to any client in the appropriate SAP
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
3. On the Process Overview screen, find the process which mustbe 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 theProcess
Overview screen until the stopped process has cleared from the
display.5. 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 SAPinstance and\or possibly the serve.
Increasing or Decreasing the Number of Work
Processes
1. Log on to any client in the appropriate SAPsystem.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 thedropdown, or whatever instance profile you need tochange. In the Edit profile section, click the radio button tothe left of Extended maintenance. Click the Change button.5. On the Maintain R/3 Profile screen, locate thedialog processes r disp\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 toclick the Copy button after each change. When all thechanges have been made, click the white arrow on greenpicture-icon.6. On the Edit Profiles screen, click the Savepicture-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 thegreen √ button.
7/23/2019 SAP BASIS Tutorial 1 - Windows - SAP BASIS Administration and Learning Tutorials
11. If you receive a Possible Inconsistencies in OPModes screen, double click over the <No> unless you areunsure of why this message has been displayed.12. You will not get a confirmation message. You maynow leave the RZ10 transaction.