This document is the intellectual property of Jo Spencer and may not be edited without permission.Symbol Legend: Press Enter System ID lower case System ID upper case

How do I....?Backups....what do I need to backup? ....how often do I need to backup? ....what are my backup options?

Client Tasks....add a client? ....add a logical system ID to be assigned to a client? ....change a client? ....copy one client to another in the same R/3 system? ....copy one client to another in different R/3 systems? ....copy only user master data from one client to another? ....delete a client? ....lock a client so configuration changes cannot be made? ....verify that a client copy ran successfully? ....view all past client copies for a client?

Communications Tasks....add a RFC connection? ....delete a RFC connection? ....modify a RFC connection? ....verify one R/3 system is talking to another?

Database Tasks....perform Database Stats, Check Database, and Backup Jobs MS SQL Server? ....perform Database Stats, Check Database, and Backup Jobs Oracle?

Job Tasks....change the start time/date for a scheduled job? ....clean out old job logs? ....delete a scheduled job? ....delete a running job? ....schedule a new job to run? ....verify that a job has run successfully?

Printer Tasks....add a printer? ....create a new Frontend aka Local aka Desktop Printer? ....reprint a document that has already printed? ....reroute a printer output request? ....reset the cache for a printer? ....view a list of all printer output requests?

This document is the intellectual property of Jo Spencer and may not be edited without permission.....view a list of the output requests for one printer only?

Security Tasks....attach a role to a user? ....attach a user to a role? ....copy an existing role to a new role? ....create a user role? ....delete a user role? ....grant a transaction to a user? ....modify a user role? ....move roles from one client to another? ....revoke an authorization from a user? ....revoke a transaction from a user?

Support Package and Binary Patch Tasks....apply a SPAM/SAINT update? ....apply kernel patches? ....apply other SAP binary patches? ....apply support packages? ....check for New SPAM Updates, Support Packages and Kernel Patches? ....download a kernel patch from SAP Marketplace? ....download a SPAM/SAINT Update? ....download a support package from SAP Marketplace? ....download other SAP binary patches? ....find your Current SPAM Update and Support Package Level ....know when SAP releases new fixes for our SAP software? ....ready a kernel patch for application? ....find SAPs most current patches? ....find your Current Kernel Patch Level? ....find your Current SPAM Update and Support Package Level? ....know when SAP releases new fixes for our SAP software? ....ready a kernel patch for application? ....ready a SPAM/SAINT update or Support Package for application? ....ready other SAP binary patches for application?

System Tasks....add a system parameter? ....apply a SAP (OSS) note? ....check that the system parameters are valid? ....delete a system parameter? ....generate a developers key for a programmer? ....generate an object key to change a SAP-owned object? ....how do I make server files viewable from SAP? ....keep all users out of a transaction? ....modify a system parameter? ....open a service connection for SAP to come into my system? ....reclaim system space from obsolete temporary objects? ....recompile all ABAP programs in a R/3 system? ....send a message to all connected users? ....send a message to one connected user? ....start R/3? ....start saprouter (OSS Link)? ....start the OS collector? ....stop a SAP work process? ....stop R/3? ....stop saprouter?

This document is the intellectual property of Jo Spencer and may not be edited without permission.....stop the OS collector? ....stop the R/3 subsystem? ....verify that our link to SAP is up? ....verify that R/3 is up? ....verify the status of saprouter? ....view a short dump received by a user? ....view all processes currently running? ....view all system locks? ....view all table locks? ....view all update locks?

Transport Tasks....add a change request to a transport queue? ....add a new SAP Instance to an Existing TMS Domain? ....automate the Transport Process? ....configure TMS Transport Management System for the First Time? ....configure TMS to Use SAP's Quality Assurance Functionality? ....re-Transport One or Several Change Requests at Once? ....transport a change from one R/3 system to another? ....transport several change requests at once? ....verify that the transport system is up and running? ....view a history of what changes have been transported? ....use Target Groups to Transport to Mulitple Clients to Different Instances?

User Tasks....add a user? ....add an ITS user? ....change a users password? ....change several users at once? ....copy an existing user to a new user? ....delete a user? ....delete an ITS user? ....drop a connected user? ....get a list of all users in a client? ....lock a user? ....lock all users at once? ....modify a user? ....modify an ITS user? ....produce various user reports? ....start an audit trace for a specific user? ....view a list of all users currently connected?

Web and Internet Tasks....start and stop the SAP IGS Server?

Working with the SAP Marketplace....apply a SAP License Key the new way? ....apply a SAP License Key the old way? ....check the status of a request License Key? ....find your Hardware Key? ....generate a Developers Key for a Programmer? ....generate an Object Key for a Programmer? ....open a Problem via SAP Marketplace? ....open a Service Connection for SAP Support to allow SAP access? ....request a new License Key?

This document is the intellectual property of Jo Spencer and may not be edited without permission.....request a SAP Marketplace User ID aka S Number aka OSS User ID?

What do I do if........my SAP instance wont start? ....my SAPGui session wont start? ....users say response is slow? ....I make user changes in the CUA Parent but they dont show in QAS or PRD? ....a printer has stopped printing? ....I need to apply patches to my SAP instance? ....a support package was applied and now every time a user moves from one screen to another they get a compiling message? ....I downloaded a kernel patch. Now what? ....users are getting errors via the Internet when displaying pictures? ....the development staff says that the IGS server is down? ....a user is receiving multiple X_MESSAGE errors, partial SAPGui screens, SAPLPAD errors when printing, or other Seemingly SAPGui related errors. What do I do? ....how to find important pages in the SAP Marketplace?

This document is the intellectual property of Jo Spencer and may not be edited without permission. System TasksStarting 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. The process mainly goes like this: ora logs on and starts the Oracle Listener then 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 doesnt 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 its own listener. Enough talk, here is how to start a SAP instance. 1. 2. 3. Verify that the SAP instance is down. Log on to the appropriate server as ora. Type in the following: lsnrctl start 4. 5. Log on to the same server as adm. 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. 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/adm for applicable errors.

6.

Return to Index... 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/adm directory. Sort them witj ls ltr is see the list sorted in descending order for the ease of viewing.

This document is the intellectual property of Jo Spencer and may not be edited without permission.If nothing obvious is found, go to the /usr/sap//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. Return to Index... Stopping the SAP Instance 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. 2. Log on to the appropriate server as adm. 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. Log on to the same server as ora. Type in the following: lsnrctl stop 5. 6. Log on to the same server as root. Type in the following: cd /usr/sap//SYS/exe/run ./saposcol -k 7. Log off the server.

3. 4.

Return to Index... Starting the SAP OS Collector 1. 2. Log on to the appropriate server as adm. Type in the following: cd /usr/sap//SYS/exe/run ./saposcol 3. Log off the server.

Return to Index...

This document is the intellectual property of Jo Spencer and may not be edited without permission.Stopping the SAP OS Collector 1. 2. Log on to the appropriate server as adm. Type in the following: cd /usr/sap//SYS/exe/run ./saposcol -k 3. Log off the server.

Return to Index...

BackupsYour Companys Take on Backups Backup and recovery for a SAP instance is best handled along with the other backup and recovery needs of your companys computer systems. But for those companys 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. Return to Index... What Needs to Be Backed Up? The PRD Instance Daily backup should be made for these SAP specific directories: /usr/sap/ /sapmnt/ /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:

This document is the intellectual property of Jo Spencer and may not be edited without permission./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/ 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/ /sapmnt/ 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/ 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. Return to Index...

Working with saprouterStarting saprouter (OSS Link) 1. 2. 3. 4. Log on to the appropriate server as adm. Click Start Administrative Tools Services to open a Services window. Right-click on the SAPROUTER service and click Start. You may now log off the server.

Return to Index... Verifying the Status of saprouter

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. 2. 3. Log on to the appropriate server as adm. Click Start Administrative Tools Services to open a Services window. 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 rightclick & Start the service. This should bounce your saprouter instance. You may now log off the server.

4.

Return to Index... Stopping saprouter 1. 2. 3. 4. Log on to the appropriate server as adm. Click Start Administrative Tools Services to open a Services window. Right-click on the SAPROUTER service and click Stop. You may now log off the server.

Return to Index...

Applying a SAP NoteNot 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. 2. 3. 4. Log on to client 000 in the appropriate SAP system. Go to transaction SNOTE. On the Note Assistant - Version XXX/XXXX: Worklist screen, on the top-most menu bar click Goto SAP Note download. 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. 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. To apply the SAP Note, on the Note Assistant - Version XXX/XXXX: Worklist screen double click on the downloaded SAP Note number. 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

5.

6. 7.

This document is the intellectual property of Jo Spencer and may not be edited without permission.8. is applied. When you are ready to apply the note, click on the clock picture-icon. 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. 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. A standard Make repairs in foreign namespaces... popup will appear. Click the green to continue. 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. On the Confirm changes popup, click the green to continue. 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. 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. 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.

9.

10. 11.

12. 13.

14.

15.

Return to Index...

Working with the SAP MarketplaceWhen a SAP instance is first installed, it comes with an automatical four week license. But you cant 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 emailed to you in the form of a script. But in case you dont receive this e-mail promptly, it is important to know how to obtain the newly generated key the oldfashioned way. Finding your Hardware Key 1. 2. Log on to the server containing the new SAP system as adm. Type the following, pressing enter when you are done: saplicense -get 3. 4. You will see a line reading saplicense: HARDWARE KEY = XXXXXXXXXXXXXX. Make note of this information before pressing Enter. You may now log off the server.

This document is the intellectual property of Jo Spencer and may not be edited without permission.Return to Index... Alternative Method for Finding your Hardware Key 1. 2. 3. 4. Log on to client 000 of the newly installed SAP system. Go to transaction SLICENSE. From the top-most menu bar of the SAP License Administration screen, click Goto Get hardware key. 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. You may now leave the SLICENSE transaction.

5.

Return to Index... Requesting a New SAP License Key 1. 2. 3. 4. 5. 6. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/licensekey. In the navigator tree on the right-hand side of the License Keys screen, click on mySAP Business Suite. On the License keys for mySAP Business Suite screen, click on the Request license key hyperlink. On the License key: Request screen, click the correct Installation hyperlink the mySAP Business Suite component. On the License key request: System overview screen, click the New system button. 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.

7.

Return to Index... Checking the Status of a Requested SAP License Key 1. 2. 3. 4. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/licensekey. In the navigator tree on the right-hand side of the License Keys screen, click on mySAP Business Suite. On the License keys for mySAP Business Suite screen, click on the Display license keys requested by me hyperlink. On the License key: request screen, look for your requested key. It should appear with the 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 System hyperlink to continue. 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.

5.

This document is the intellectual property of Jo Spencer and may not be edited without permission.6. You may now close your web browser session. Return to Index... Applying a SAP License Key the Old Way 1. Log on to the server that contains the new SAP system as adm. saplicense -install 2. You will be prompted license, and the new data. Once the new license applied message. If it somewhere on your license as well: for the , hardware key, expiration date of the new license. Press Enter after the entry of each piece of key has been accepted, you will received a License key you have the TXT file SAP e-mailed you, you can place server and use the following syntax to install the

3.

saplicense install ifile= 4. You may now log off the server.

Return to Index... Applying a SAP License Key the New Way 1. 2. 3. 4. Log on to client 000 in the SAP system in which the new license key is to be installed. Go to transaction SLICENSE. From the top-most menu bar on the SAP License Administration screen, click Edit Install license. 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. You will receive a License key successfully installed message. You may now leave the SLICENSE transaction.

5.

Return to Index... Generating a Developers Key for a Programmer 1. 2. 3. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/sscr. In the navigator tree on the right-hand side of the SSCR screen, click on Registration. 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. On the SSCR Register Developer screen, type in the developers SAP user ID and click the Register button. A new Details section will appear. Note the generated developers key or cut-and-paste for other storage. You may now close your web browser session.

4. 5. 6.

Return to Index...

This document is the intellectual property of Jo Spencer and may not be edited without permission.Generating an Object Key to Change a SAP-owned Object 1. 2. 3. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/sscr. In the navigator tree on the right-hand side of the SSCR screen, click on Registration. 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. 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. A new Details section will appear. Note the generated object key or cutand-paste for other storage. You may now close your web browser session.

4.

5. 6.

Return to Index... 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. 2. 3. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/serviceconnection. On the Service Connections screen, click the Service Connections button. 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 instances line. In the Enter Data for the systems semi-automatic opening popup, set the days, hours, and minutes you want the service connection to stay open. Click the Continue button.

4.

This part is being rewritten to meet the new SAP procedures. Return to Index... Problem Logging with SAP Support Reporting a Problem to SAP 1. 2. 3. 4. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/message. On the Create Customer Messages screen, click on the Start Message Wizard button. On the Customer messages Create screen, click the Select a System button. 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

This document is the intellectual property of Jo Spencer and may not be edited without permission.of system, click on the radio button just left of the for which you are reporting the problem. Click the Choose button and you will be returned to the Customer messages Create screen. 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. 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 Addon 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 systems information from the appropriate dropdowns. Click the Continue hyperlink. 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. 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. 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. When you have provided as much information as possible, click the Send to SAP hyperlink. You will receive a confirmation screen with a generation problem number. Write this problem number down for later use. You may now leave the Message Wizard and close the web browser window.

5.

6.

7.

8.

9.

10. 11. 12.

Return to Index... Checking the Status of a Reported Problem 1. 2. 3. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/message. Click on Customer Messages. All the open OSS problems you have sent to SAP will appear here. You may now leave the Message Wizard and close the web browser window.

Return to Index... Creating, Modifying, Deleting, Transporting, and Resetting Print Devices Creating a Print Device 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SPAD. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. 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. 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. You may now leave the SPAD transaction.

5.

6.

7.

Return to Index... Modifying a Print Device 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SPAD. 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 the pencil picture-icon to switch into change mode. Double click on the output device to be changed. 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 pictureicon. 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. You may now leave the SPAD transaction.

5.

6.

7.

Return to Index... Deleting a Print Device 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SPAD. 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 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. On the Spool admin.: Delete screen, verify that the correct printer is about to be deleted. Click the Yes button. 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.

5. 6.

Return to Index... Transporting a Printer or a Group of Printers 1. 2. Log on to any client in the appropriate SAP system. Go to transaction SPAD.

This document is the intellectual property of Jo Spencer and may not be edited without permission.3. 4. 5. 6. 7. 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 the pencil picture-icon to switch into change mode. Click on an output device to be transported and then click the truck picture-icon. On the Spool Administration: List of Output Devices (Change) popup, click the green picture-icon. 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. 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. You may now leave the SPAD transaction.

8.

9.

Return to Index... 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. 2. 3. 4. 5. 6. 7. 8. 9. Log on to any client in the appropriate SAP system. Go to transaction SPAD. 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, double click on the printer you need to reset. On the Spool Administration: Output Device (Display) screen, click on the pencil picture-icon to switch from display mode to change mode. On the Administration: Output Device (Change) screen, on the top-most menu bar click Edit Reactivate. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit Reset Cache. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit NI Reset. You may now leave the SPAD transaction.

Return to Index...

Printer OutputCreating 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. 1. Log on to any client in the appropriate SAP system.

This document is the intellectual property of Jo Spencer and may not be edited without permission.2. 3. 4. 5. Go to transaction SPAD. On the Spool Administration: Initial Screen screen, click the Output Devices button. On the Spool Administration: List of Output Devices screen, click the Change button and then the Create button. 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 6. Save the printer. 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. Return to Index... Viewing a List of Pending Printer Output Requests for All Printers 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SP01. On the Output Controller: Spool request selection Screen screen, click on the Output requests tab. 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. A list of all pending output requests will be displayed. You may now leave the SP01 transaction.

5. 6.

Return to Index... Viewing a List of Output Requests for a Specific Printer 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SPAD. 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. A list of all pending output requests for the selected printer will be displayed. You may now leave the SPAD transaction.

4. 5.

Return to Index... Reprinting a Document

This document is the intellectual property of Jo Spencer and may not be edited without permission.1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SP01. 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. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted. Click on the printer picture-icon. An Output request created message should appear in the bottom status bar. You may now leave the SP01 transaction.

4. 5. 6.

Return to Index... Re-routing Print to a Different Printer 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SP01. 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. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted. 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. On the Output control: Save attributes popup, click the Yes button. On the Confirm redirection of output popup, click the Yes button. An Output request created message should appear in the bottom status bar. You may now leave the SP01 transaction.

4. 5.

6. 7. 8.

Return to Index...

Deleting Obsolete Temporary Objects and Reclaiming the Space1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SP12. On the TemSe --- Administration of Temporary Sequential Data screen, on the top-most menu bar click TemSe database Reorganization. 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. On the TemSe objects older than XX days popup, click the Yes button. 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. You may now leave the SP12 transaction.

5. 6.

7.

Return to Index...

Mass Recompilation of ABAP Programs1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SGEN. On the SAP Load Generator screen - Generation task section, click on the line reading Generate all objects in selected software components to turn

This document is the intellectual property of Jo Spencer and may not be edited without permission.4. on the radio button to the left. Click on the Continue button at the bottom. 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. 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. 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. 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.

5.

6.

7.

Return to Index...

SAP IGS ServerThe 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 Log on to the appropriate server as adm. Type the following: cd /usr/sap//DVEBMGS00/igs ./bin/startigs -p . 3. You may log off the server.

1. 2.

Stopping the IGS instance 4. 5. Log on to the appropriate server as adm. Type the following: cd /usr/sap//DVEBMGS00/igs ./bin/stopigs 6. You may log off the server.

Return to Index...

Support Tasks in the SAP MarketplaceSome adminitrative tasks performed on the SAP Marketplace are instantaneous such as SSCR (SAP Source Correction Registration)

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/user-admin. 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. 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. You may now log off the SAP Marketplace.

2. 3.

4.

5.

Return to Index... Checking A New SAP Marketplace User ID aka S Number aka OSS ID 1. 2. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/user-admin. 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. 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. 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. You may now log off the SAP Marketplace.

3.

4.

5.

Return to Index... 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. 2. Log on to the SAP Marketplace using an OSS ID with Administration rights http://service.sap.com/user-admin. 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.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. From the second User Data Maintenance screen, click on the Surname of any user you wish to change. 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. 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. 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. 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. 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. You may now log off the SAP Marketplace.

4. 5. 6.

7.

8.

9.

10.

Return to Index...

Creating, Modifying, and Deleting System ParametersCreating System Parameters 6. 7. 8. Log on to any client in the appropriate SAP system. Go to transaction RZ10. On the Edit Profiles screen, select the _DVEBMGS00_SAP 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. On the Maintain R/3 Profile screen, click the Add Parameter button. 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. On the Maintain R/3 Profile popup, click the Yes button to save your changes. On the Edit Profiles screen, click the Save picture-icon. On the Save profile popup, click the No button. On the Activate profile popup, click the Yes button. On the Edit Profiles popup, click the green button. On the Caution! Caution! Caution! popup, click the green button. If you receive a Possible Inconsistencies in OP Modes screen, double click over the unless you are unsure of why this message has been displayed. You will not get a confirmation message. You may now leave the RZ10 transaction.

9. 10.

11. 12. 13. 14. 15. 16. 17. 18.

Return to Index... Modifying System Parameters 1. 2. Log on to any client in the appropriate SAP system. Go to transaction RZ10.

This document is the intellectual property of Jo Spencer and may not be edited without permission.3. On the Edit Profiles screen, select the _DVEBMGS00_SAP 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. 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. On the Edit Profiles screen, click the Save picture-icon. On the Save profile popup, click the No button. On the Activate profile popup, click the Yes button. On the Edit Profiles popup, click the green button. On the Caution! Caution! Caution! popup, click the green button. If you receive a Possible Inconsistencies in OP Modes screen, double click over the unless you are unsure of why this message has been displayed. You will not get a confirmation message. You may now leave the RZ10 transaction.

4.

5. 6. 7. 8. 9. 10. 11.

Return to Index... Deleting System Parameters 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction RZ10. On the Edit Profiles screen, select the _DVEBMGS00_SAP 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. 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. 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. On the Edit Profiles screen, click the Save picture-icon. On the Save profile popup, click the No button. On the Activate profile popup, click the Yes button. On the Edit Profiles popup, click the green button. On the Caution! Caution! Caution! popup, click the green button. If you receive a Possible Inconsistencies in OP Modes screen, double click over the unless you are unsure of why this message has been displayed. You may now leave the RZ10 transaction.

4.

5.

6. 7. 8. 9. 10. 11. 12.

Return to Index... Overview of All Work Processes Running on a SAP System 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SM50. 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.

This document is the intellectual property of Jo Spencer and may not be edited without permission.4. 5. 6. Click on the blue arrow circle picture-icon to refresh the process data appearing on the screen. Click the white clock picture-icon to display the amount of CPU time consumed by each process thread so far. 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. 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. You may now leave the SM50 transaction.

7.

8.

Return to Index... Stopping Run-Away or Bad Work Processes 1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SM50. 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. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. You may now leave the SM50 transaction.

4. 4.

If this does not kill the process, you can go to transaction SM04 and kill the users 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. Return to Index... Increasing or Decreasing the Number of Work Processes 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction RZ10. On the Save profile popup, click the No button. On the Edit Profiles screen, select the _DVEBMGS00_SAP 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. 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. On the Edit Profiles screen, click the Save picture-icon. On the Save profile popup, click the No button.

5.

6. 7.

This document is the intellectual property of Jo Spencer and may not be edited without permission.8. 9. 10. 11. 12. On the Activate profile popup, click the Yes button. On the Edit Profiles popup, click the green button. On the Caution! Caution! Caution! popup, click the green button. If you receive a Possible Inconsistencies in OP Modes screen, double click over the unless you are unsure of why this message has been displayed. You will not get a confirmation message. You may now leave the RZ10 transaction.

Return to Index...

Broadcasting System MessagesCreating a System Message 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SM02. On the System Messages screen, click the Create button. 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. A System message added message will appear in the bottom status bar. You may now leave the SM02 transaction.

5.

Return to Index... Modifying a System Message 1. 2. 3. 4. 5. 6. Log on to any client in the appropriate SAP system. Go to transaction SM02. On the System Messages screen, double click on the Id number of the message that needs to be changed. On the Display System Messages popup, click the pencil and glasses pictureicon to switch to change mode. On the Change System Messages popup, make your changes and click the green to save the changed message. A System message changed message will appear in the bottom status bar. You may now leave the SM02 transaction.

Return to Index... Deleting a System Message 1. 2. 3. 4. 5. Log on to any client in the appropriate SAP system. Go to transaction SM02. 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. On the System message: Delete popup, click the Yes button to delete the message. A System message deleted message will appear in the bottom status bar. You may now leave the SM02 transaction.

Return to Index...

This document is the intellectual property of Jo Spencer and may not be edited without permission.Sending a System Message to a Single User 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SE37. On the Function Builder: Initial Screen screen, type in the Function name TH_POPUP. Click the Single Test wrench picture-icon. 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. You may now leave the SE37 transaction.

5.

Return to Index...

Locking R/3 Transactions1. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction SM01. 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. 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. The transaction is now locked. You may now leave the SM01 transaction.

4.

5.

Return to Index...

Short Dump AnalysisShort 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. 2. 3. Log on to any client in the appropriate SAP system. Go to transaction ST22. On the ABAP runtime errors screen, you can click the Today button for todays dumps, the Yesterday button for yesterdays 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. On the List of Selected Runtime Errors screen, double-click on any short dump you want to examine more closely. 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. You may now leave the ST22 transaction.

4. 5.

6.

Return to Index... Viewing Database Lock Information 1. 2. Log on to any client in the appropriate SAP system. Go to transaction DB01.

This document is the intellectual property of Jo Spencer and may not be edited without permission.3. 4. The information displayed on the Oracle Lock Monitor screen can be sorted and filtered to meet your reporting requirements. You may now leave the DB01 transaction.

Return to Index... Viewing Table Lock Information 1. 2. 3. 4. Log on to any client in the appropriate SAP system. Go to transaction SM12. 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. 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. You may now leave the SM12 transaction.

5.

Return to Index... 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. Log on to any client in the appropriate SAP system. Go to transaction SM13. 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 arent that many hanging update locks at one time, so dont worry about being too specific. When you have entered all your information, press Enter. 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. 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. 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.

1. 2. 3.

4.

5.

6.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. You will not receive a confirmation message after the update or delete. You may now leave the SM13 transaction.

8.

Return to Index... Viewing OS Server Files from SAP 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. Return to Index...

Transport TasksConfiguring TMS - Transport Management System - for the First Time 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 preexisting transports, making them untransportable. Instead, use the following section Adding New Instance to TMS Setup. 1. 2. 3. 4. 5. 6. 7. Log on to client 000 of the SAP instance to serve as the Domain Controller. Go to transaction SE06. Click on the Perform Post Installation Actions button. Go to transaction STMS. 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. Fill in the TMS: Configure Transport Domain popup with the Description, Name of DOMAIN_, and the description of the Transport Domain. Then click Save. On the Transport Management System screen (if you arent 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. On the System Overview Domain Domain_ 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 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 \\:\usr\sap\trans for NT or /usr/sap/trans for UNIX. Click Environment Transport Routes. On the Display Transport Routes screen, click the User Settings button, turn on the Hiergraphical List Editor, and click the Continue button. Back out

8.

9.

This document is the intellectual property of Jo Spencer and may not be edited without permission.10. 11. 12. 13. 14. 15. 16. of the screen and then go back in you should see the list in a text mode which makes it easier to handle. On the Display Transport Routes screen, click the DisplayChange button to toggle into Change Mode. On the Change Transport Routes screen, click Configuration Standard Configuration Development and Production System. 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. Back on the Change Transport Routes screen, click the Save icon and confirm all the popup questions. On the Change Transport Routes screen, back out until you can once more see the Transport Management System screen. Click Overview Systems. On the Display TMS Configuration: System XXX screen, double-click the TMS Domain domain controller SAP instance. On the Display TMS Configuration: System XXX screen, click the DisplayChange 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_ where 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. 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. Save your way back the the main STMS screen. You may now leave STMS.

17. 18. 19.

Return to Index... Adding a New SAP Instance to an Existing TMS Domain Controller 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 DisplayChange 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 1.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. Return to Index... Make a Local Transport into a Transportable Transport 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. Return to Index... 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.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. Return to Index... Adding a Change Request to a Transport Queue 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. Return to Index... Viewing the Transport Queue History 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. Return to Index... Re-Transport Several Change Requests at Once1.

2.

3. 4.

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. 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. Once all choices have been made, click Request Forward System. Fill in the TO system and click on the Execute green mark. Now you can go to the TO queue and refresh the list. Your imports should all be there.

Return to Index... Transport Tool System Confirmation

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. Return to Index... Use Target Groups to Transport to Mulitple Clients in Two Different Instances Log on to client 000 of your TMS Domain Controller SAP Instance. Go to transaction STMS. 3. On the Transport System Management screen, click Overview -> Transport Routes. 4. On the Display Transport Routes screen, click the DisplayChange 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. Return to Index... Configure TMS to Use SAP's Quality Assurance Functionality 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. 2. 3. 4. Log on to client 000 of your TMS Domain Controller SAP Instance. Go to transaction STMS. On the Transport System Management screen, click Overview -> Transport Routes. On the Display Transport Routes screen, click DisplayChange 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. 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. 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 1. 2.

5. 6.

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. Return to Index... Automate the Transport Process 1. 2. 3. 4. 5. Log on to client 000 of your TMS Domain Controller SAP Instance. Go to transaction STMS. On the Transport System Management screen, click Overview -> Imports. Double-click on the queue for the SAP instance are in. On the Import Queue screen, click the Refresh button. Click on the Import All Requests button. 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. You may now leave the STMS transaction. If you ever need to change this job, you must do it via STMS and not SE37.

6.

Return to Index...

User TasksCreating, Modifying, and Deleting Users Creating a User 1. 2. 3. 4. Log on to the appropriate SAP system and the client where the new user is to be added. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the new User name and click the blank page picture-icon. On the Maintain User screen, fill in at least the following information for each tab: Address Logon data Last name, First name, Internet mail Initial password, repeat password, user type

This document is the intellectual property of Jo Spencer and may not be edited without permission.Defaults Roles Profiles Decimal formation, Date formation, Time zone, OutputDevice Select roles to be added to the user Select profiles to be added to the user

5.

When all necessary data has been entered, click the Save picture-icon. You will receive a User saved message in the status bar at the bottom of the screen. You may now leave the SU01 transaction.

Return to Index... Copy an Existing User to a New User 1. 2. 3. 4. 5. Log on to the appropriate SAP system and the client where the user is to be changed. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the User name to be copied and click the double blank page picture-icon. On the Copy User popup, type in the To for the new user and click the Copy button. On the Maintain User screen, click on the tabs and make the changes to the users 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. You may now leave the SU01 transaction.

6.

Return to Index... Modifying a User 7. 8. 9. 10. 11. Log on to the appropriate SAP system and the client where the user is to be changed. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the users name and click the pencil picture-icon. On the Maintain User screen, click on the tabs and make your user information changes. 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. You may now leave the SU01 transaction.

Return to Index... Deleting a User 1. 2. 3. 4. 5. Log on to the appropriate SAP system and the client where the user is to be deleted. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the users name and click the trash can picture-icon. On the Delete user popup, click the Yes button. You will receive a User deleted message in the status bar at the bottom of the screen. You may now leave the SU01 transaction.

Return to Index...

This document is the intellectual property of Jo Spencer and may not be edited without permission.Locking a User 1. 2. 3. 4. 5. Log on to the appropriate SAP system and the client where the user is to be locked. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the users name and click the lock/unlock picture-icon. On the Lock user popup, click the lock picture-icon. You will receive a User locked message in the status bar at the bottom of the screen. You may now leave transaction SU01.

Return to Index... Modifying a Users Password 1. 2. 3. 4. 5. Log on to the appropriate SAP system and the client where the users password is to be changes. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the users name and click the lock/unlock picture-icon. On the Change Password popup, enter the new password in both the New password and Repeat password boxes. Click the green picture-icon. 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.

Return to Index... Add a Role to a User 1. 2. 3. 4. 5. 6. Log on to the appropriate SAP system and the client where the user needs the role. Go to transaction SU01. On the User Maintenance: Initial Screen screen, type in the users name and press Enter to confirm that the user exists. Click the Change button or press Shift+F6. 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. Click the Save button. 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. Click the Change role little yellow pencil button. 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!

7. 8.

Return to Index... Mass User Changes 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

This document is the intellectual property of Jo Spencer and may not be edited without permission.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. 2. 3. Log on to the appropriate SAP system and the client where the user changes are to take place. Go to transaction SU10. 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. 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. 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. 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. On the Mass changes popup, you will see how many users you are about to change. To make the changes, click on Yes. On the Log Display screen, you will see a log of the changes you made. Expand the list to see the transactional details. You may now leave the SU10 transaction.

4.

5.

6.

7. 8. 9.

Return to Index... User Information Repository Reports 1. 2. 3. Log on to the appropriate SAP system and client where the user reports are to be generated. Go to transaction SUIM. 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. 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. You may now leave the SU01 transaction.

4.

5.

Return to Index... User Information Repository Reports 6. 7. 8. Log on to the appropriate SAP system and client wh