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. Verifying that the SAP Instance is up
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.
==================================================================================== See also
http://sites.google.com/site/saparchives/Home-SAP-BASIS http://sites.google.com/site/saparchives/sap-basis-transactions http://sites.google.com/site/saparchives/Home-SAP-BASIS/SAP-BASIS--unknown-sap-tricks http://sites.google.com/site/saparchives/SAP-BASIS-everything-about-sap-clients http://sites.google.com/site/saparchives/frequently-used-procedures http://sites.google.com/site/saparchives/SAP-BASIS-BASICS http://sites.google.com/site/saparchives/SAP-BASIS-what-is-asap http://sites.google.com/site/saparchives/SAP-BASIS-configuration http://sites.google.com/site/saparchives/SAP-basis-operation---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-2---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-1---windows http://sites.google.com/site/saparchives/SAP-basis-operation-2---windows http://sites.google.com/site/saparchives/SAP-basis-operation-3---windows http://sites.google.com/site/saparchives/SAP-basis-interview-questions http://sites.google.com/site/saparchives/sap-training-courses-ecc-60 http://sites.google.com/site/saparchives/sap-basis-refference-steps-1 http://sites.google.com/site/saparchives/SAP-basis-transactions ====================================================================================== 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.
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’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.
Alternative Method for Finding your Hardware Key
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. You may now close your web browser session.
Checking the Status of a Requested 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 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.
Applying a SAP License Key the New Way
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. Generating a Developer’s Key for a Programmer
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. Generating an Object Key to Change a SAP-owned Object
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. Opening a Service Connection for SAP Support
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 – 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 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 – http://service.sap.com/message. 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.
Creating, Modifying, Deleting, Transporting, and Resetting Print Devices
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. Transporting a Printer or a Group of Printers
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.
Resetting the Cache for a Printer
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.
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 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. 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:
And the following Access Method fields:
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.
Viewing a List of Pending Printer Output Requests for All Printers
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. Re-routing Print to a Different Printer
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.
Deleting Obsolete Temporary Objects and Reclaiming the Space
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. Mass Recompilation of ABAP Programs
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, 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 of something 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 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.
Creating, Modifying, and Deleting 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 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, click the Add Parameter button. 5. 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. 6. On the Maintain R/3 Profile popup, click the Yes button to save your changes. 7. On the Edit Profiles screen, click the Save picture-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 the green √ button. 12. 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. 13. 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. Overview of All Work Processes Running on a SAP System
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.
Stopping Run-Away or “Bad” Work Processes
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. See also http://sites.google.com/site/saparchives/Home-SAP-BASIS http://sites.google.com/site/saparchives/sap-basis-transactions http://sites.google.com/site/saparchives/Home-SAP-BASIS/SAP-BASIS--unknown-sap-tricks http://sites.google.com/site/saparchives/SAP-BASIS-everything-about-sap-clients http://sites.google.com/site/saparchives/frequently-used-procedures http://sites.google.com/site/saparchives/SAP-BASIS-BASICS http://sites.google.com/site/saparchives/SAP-BASIS-what-is-asap http://sites.google.com/site/saparchives/SAP-BASIS-configuration http://sites.google.com/site/saparchives/SAP-basis-operation---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-2---unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux http://sites.google.com/site/saparchives/SAP-basis-operation-1---windows http://sites.google.com/site/saparchives/SAP-basis-operation-2---windows http://sites.google.com/site/saparchives/SAP-basis-operation-3---windows http://sites.google.com/site/saparchives/SAP-basis-interview-questions http://sites.google.com/site/saparchives/sap-training-courses-ecc-60 http://sites.google.com/site/saparchives/sap-basis-refference-steps-1 http://sites.google.com/site/saparchives/SAP-basis-transactions SAP BASIS - INDIA
|
SAP BASIS Tutorial 1 - Unix & Linux |