.

Symbol Legend: ¬ Press Enter <sid> System ID lower <SID> System ID upper

case 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? ....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 SAP’s 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 developer’s 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? ....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 user’s 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 Developer’s 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?

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

the script simply moves on to the next step. . Even if you have multiple SAP instances on a server. Enough talk. If it has not had a successful start up. Wait until the startup messages have scrolled by. it doesn’t matter. If saposcol is up and running. Then only one Oracle Listener is used since both databases share one Oracle listening port which is normally 1527. 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. check the logs in the /home/<sid>adm for applicable errors. Type in the following: lsnrctl start¬ 4. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. 3. type instead: startsap DB¬ 6. the process is pretty much the same unless the Oracle databases were installed using the MCOD installation option. And do not do the rest of the start up procedures listed below. Verify that the SAP instance is down. go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. 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. dev_disp. There may be other minor programs that start at the time as well. 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. you can stop now. Log on to the appropriate server as ora<sid>. here is how to start a SAP instance. System Tasks Starting the SAP Instance The normal SAP instance start up consists of three parts: starting the SAP OS Collector.. When the SAP Instance starts up via the startsap script. starting the Oracle Listener. 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. 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. 2. dev_rfcx. look at the logs in the /home/<sid>adm directory. and stderrx files. If nothing obvious is found. and starting the SAP instance. If you try to logon and are refused connection. Log on to the same server as <sid>adm. If it is not.. Normally each SAP database – ie SAP instance .. Return to Index. 1.has it’s own listener. So the SAP OS Collector gets handled one way or another. dev_ms. The most useful information can be found in the dev_wx. the script starts saposcol as root and then proceeds.

Log on to the appropriate server as <sid>adm. Log on to the same server as root.. 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. 6. The only real difference is that the stopsap script will NOT stop the SAP OS Collector for you.. Log on to the same server as ora<sid>. Type in the following: cd /usr/sap/<SID>/SYS/exe/run¬ . Stopping the SAP OS Collector 1. please refer to the section SAP System Start Up Troubleshooting.. you can stop now. And do not do the rest of the start up procedures listed below. and stop the SAP OS Collector. Starting the SAP OS Collector 1. 1. 2. stop the SAP instance. Type in the following: cd /usr/sap/<SID>/SYS/exe/run¬ . Return to Index. Log on to the appropriate server as <sid>adm. Stopping the SAP Instance The stopping of a SAP instance is practically the reversal of the start up Process. Return to Index. Log on to the appropriate server as <sid>adm. 4. Type in the following: stopsap¬ If you only need to stop the SAP instance and not the database too.. Type in the following: lsnrctl stop¬ 5. Log off the server../saposcol¬ 3. type instead: stopsap R3¬ 3./saposcol -k¬ 7. If you need further assistance. Return to Index. Log off the server. Type in the following: cd /usr/sap/<SID>/SYS/exe/run¬ . stop the Oracle Listener. 2.. 2.

Log off the server. 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. This is the same transaction where weekly statistics. are all decisions your IT staff need to make based on their history with similar procedures at your company. and database verification jobs are scheduled in the post-installation work after installation of a new SAP instance. . But for those company’s who do not yet possess a solid backup and recovery solution. transaction DB13 can be used to schedule periodic backups. If your company falls into the latter category. Index Rebuilds. More information regarding BRCONNECT can be found in the SAP BRCONNECT Guide which can be found at http://service. log cleanup.sap. frequency.. here are a few things you need to know. high availability. and the guidance of your implementation Basis consultant. Enforced backups.. If you SAP server contain a tape drive or has access to the network tape unit..com/instguides. or who simply want to segragate the SAP landscape from all other internal IT solutions. and a documented part of any SAP implementation project. For more information. Backups Your Company’s Take on Backups Backup and recovery for a SAP instance is best handled along with the other backup and recovery needs of your company’s computer systems. Return to Index. and Log Backup Jobs – Oracle. and detailed and tested recovery procedures should be part of any Disaster Recovery plan. 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 .. Online versus offline. SAP does supply tools for your uses which can be used in either line command form or from within the SAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed in command line form by the IT staff.. the recommendations of SAP. Return to Index./saposcol -k¬ 3.

. and each separate /oracle/<SID> directory if there is more than one instance on the server. Right-click on the SAPROUTER service and click Start. Log on to the appropriate server as <sid>adm. there can only be three reasons for a “broken” SAPNet connection to SAP: the SAP VPN is down (which rarely happens).. 2. Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past. .. 2. and each separate /oracle/<SID> directory if there is more than one instance on the server. the entire /oracle directory should be backed up daily if there is only one Oracle 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. your saprouter configuration has been incorrectly changed (also very rare). Click Start → Administrative Tools → Services to open a Services window. Working with saprouter Starting saprouter (OSS Link) 1. or your saprouter is not running (happens all the time). the entire /oracle directory should be backed up daily if there is only one Oracle Instance on the server.. It is also recommended that a full offline image of the entire server be made before the monthly closing cycle. Return to Index. Return to Index. Log on to the appropriate server as <sid>adm. 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. 3. 4. 1. Click Start → Administrative Tools → Services to open a Services window.. You may now log off the server. For Oracle.

Log on to the appropriate server as <sid>adm. Once the SAP Note has been downloaded. Right-click on the SAPROUTER service and click Stop. If is not started. Applying a SAP Note Not all SAP Notes can be applied via the SNOTE transaction. 7. You may now log off the server. on the Note Assistant . Others entail corrections that can only be done manually. on the top-most menu bar click Goto → SAP Note download. Return to Index. 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. Use the SNOTE transaction in each SAP system that needs the correction. a list will appear in a SAP Note queue to be Imported popup. A SAP Note XXXXXX is being downloaded message will appear in the bottom status bar. Click the clock picture-icon to download these prerequisite SAP Notes as well. To apply the SAP Note.. Also.Version XXX/XXXX: Worklist screen. it will appear on the Assistant . If you get a communications error message. SAP recommends that SNOTE change requests NOT be transported into other systems. When you are ready to apply the note. 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.. 2. If there is a gray diamond instead. On the Note Assistant: Download Note popup..Version XXX/XXXX: Worklist screen double click on the downloaded SAP Note number. On the Note Assistant – Display Note XXXXXX screen.Version XXX/XXXX: Worklist screen under the SAP Notes → New navigation tree. 8. 2. 4. right-click to start the service. On the Note Assistant . type the number of the SAP note in the Note number box and click the clock picture-icon. providing no code corrections. 4. 3. click on the clock picture-icon. a list will appear in a Load the following notes into your SAP system popup will appear. The SAP Note can only be applied if there is a blue box with a black arrow to the left of the note number. Stopping saprouter 1. 4. If it is started. read the note text to see if there are any necessary manual tasks to be performed after the note is applied. 6. Go to transaction SNOTE. 5. Some are information only. Click Start → Administrative Tools → Services to open a Services window. . 3. This latter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAP programmer. If any of the prerequisite SAP Notes must be applied in parallel with the original downloaded SAP Note. Log on to client 000 in the appropriate SAP system. Return to Index. 1. If there are any prerequisite SAP Notes which need to be applied to the SAP system before the downloaded SAP Note can be applied.. the downloaded note cannot be applied or is not application for this SAP system. Click the clock picture-icon to apply all the listed SAP Notes. You may now log off the server. right-click & Stop the service and then right-click & Start the service. If you do not have a working OSS connection.. 3. This should “bounce” your saprouter instance. verify that saprouter is up and try again. Look at the SAPROUTER service.

Return to Index. 11. may require recompilation. Log on to client 000 of the newly installed SAP system. 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. it comes with an automatical four week license.. you will be returned to the Note Assistant . click the blank page pictureicon to create a new change request.. Click the green √ and pencil picture-icon. Make note of this information before pressing Enter. click Goto → Get hardware key. Log on to the server containing the new SAP system as <sid>adm. The license key request process has been drastically overhauled by SAP over the past. functions. 2. Before applying any SAP Notes to your SAP system. 13. Return to Index. You may now log off the server. 12. the information will be e-mailed to you in the form of a script. After the SAP Note has been applied to the SAP system.. Go to transaction SLICENSE. Modified programs. If the OSS note you applied changed a ABAP program. Alternative Method for Finding your Hardware Key 1. You can now leave the SNOTE transaction. click on the Completed line to turn “on” the radio button. A standard Make repairs in foreign namespaces.. Finding your Hardware Key 1. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. 15. Normally. But you can’t install any kind of SSCR key on a termporary instance. fill in the Short description and click the Save picture-icon. click the green √ to continue. a Confirmation: SAP Note read popup will appear. click the Yes button. 14.. There is no completion message. Once you have read the information contained in this popup. etc.. You will see a line reading “saplicense: HARDWARE KEY = XXXXXXXXXXXXXX”. 4. But in case you don’t receive this e-mail promptly. 9. 2. On the Prompt for transportable Workbench request popup. On the Set Processing Status for Note XXXXXX popup.Version XXX/XXXX: Worklist screen. 10. if you request a new SAP license key. On the Confirm changes popup. it is important to know how to obtain the newly generated key “the old-fashioned way”. so it is best to get the permanent license key immediately. . Working with the SAP Marketplace When a SAP instance is first installed. you must go to the SE38 transaction and manually recompile the program. popup will appear. Click the green √. Click the green √ to continue. From the top-most menu bar of the SAP License Administration screen. pressing enter when you are done: saplicense -get 3. If it changed a function.. Type the following. 3. Click the green √ to continue. On the Create Request popup.

On the License keys for mySAP Business Suite screen. In the License request section. fill in the required information in the System section. It should appear with the <SID> you provided during the request process..sap. Write this key down and remember that it is case sensitive. click the New system button. If the Status shows as Completed. After you have supplied the hardware key. fill in the Hardware key box right above the Save New Item button. 2. In the navigator tree on the right-hand side of the License Keys screen.sap. Return to Index. You may now leave the SLICENSE transaction. Applying a SAP License Key the Old Way 1. Or you can cut-and-paste it to a more convenient storage location. Checking the Status of a Requested SAP License Key 1. On the License key: Request screen. The hardware key will appear in the box to the right of the Detrmne button.. click on the Display license keys requested by me hyperlink.. 4. 2. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. On the License keys for mySAP Business Suite screen. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. . Return to Index. Click the Detrmne button to continue. On the License key: request screen. the license key has not yet been generated.. In the navigator tree on the right-hand side of the License Keys screen. You may now close your web browser session.com/licensekey. 5. your new license key has been generated and you can click on the <SID> System hyperlink to continue. 5. 6. Click the button to the left of this entry to high-bright the line. 5. Click on the □ to the left of the license request to place a √ in the box. find the host name or IP address for the new SAP system server. click on mySAP Business Suite. click on mySAP Business Suite. Under the License key header you will see you new SAP system license key.. Requesting a New SAP License Key 1. 7.com/licensekey.. On the Determine Remote Hardware Key popup. scroll down until you can see the License request section. Log on to the server that contains the new SAP system as <sid>adm. 6. On the License key request: System overview screen. click the correct Installation hyperlink the mySAP Business Suite component. 4. click the Save New Item button. Now you are finally ready to click the Send Request button.. 3. On the License key: request screen. 4. Return to Index. You may now close your web browser session. 3. click on the Request license key hyperlink. On the License key: Request for a new system screen. If the Status shows as Sent to SAP. The license key request will be shifted up to the first line of the License request list. look for your requested key.

If you need help. Note the generated developer’s key or cut-and-paste for other storage. 6. and the new license.. expiration date of the new license. In the navigator tree on the right-hand side of the SSCR screen. 3.. You will receive a License key successfully installed message. In the navigator tree on the right-hand side of the SSCR screen. Make sure you use the MS SQL installation and not R/3.. 4. On the SSCR – Registration screen. On the SSCR – Register Developer screen. You will be prompted for the <SID>. 4. Return to Index. A new Details section will appear.sap. the information can be . Once the new license key has been accepted. Or. 3. 4. click Edit → Install license.. You may now close your web browser session. Return to Index. 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. Generating a Developer’s Key for a Programmer 1. You may now log off the server. From the top-most menu bar on the SAP License Administration screen. click on Registration. Applying a SAP License Key the New Way 3. If you have the TXT file SAP e-mailed you. 3.. fill in the information necessary to generate an object key. Make sure you select the correct Installation Number for the SAP “flavor” you need or the generated key will not work. this information is contained in the Register Object popup the programmer received on his workstation.. hardware key. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. 5. 5. fill in the new license key you obtained from SAP. On the SSCR – Registration screen.com/sscr. On the SSCR – Register Object screen.sap. saplicense -install 2. Click network picture-icon to finish the new license installation. You may now leave the SLICENSE transaction. 2. Log on to client 000 in the SAP system in which the new license key is to be installed. Return to Index. On the Install New License popup. 2. Generating an Object Key to Change a SAP-owned Object 1.. click the Register object radio button and click an Installation hyperlink.com/sscr. Go to transaction SLICENSE. you will receive a License key applied message. click on Registration. click the Register developer radio button and click an Installation hyperlink. 1. if this is a repair. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. Press Enter after the entry of each piece of data. type in the developer’s SAP user ID and click the Register button. 2.

2. 5. Return to Index. be sure that the SAPAG client has been added to the appropriate SAP system and Client. scroll down to the bottom of the screen.com/message. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. Opening a Service Connection for SAP Support Before opening a service connection for SAP. This part is being rewritten to meet the new SAP procedures. Click the Continue hyperlink. select the appropriate Add-on and Add-on release from the dropdowns. On the System Selection popup. 6. selection your SAP system’s information from the appropriate dropdowns. Please LOPInstalltion. You may now close your web browser session..com/serviceconnection. On the Customer messages – Create screen. 4. .. the saprouter must run the LOP – Line Opener Program – to initiate the mode of SAP connection. High. Note the generated object key or cut-and-paste for other storage. Medium. From the Priority dropdown. Click the Register button once all information has been enter. From the Release dropdown. and minutes you want the service connection to stay open. 3. leave these dropdowns blank. On the Service Connections screen. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. click on the Start Message Wizard button. hours. A new Details section will appear.. Click the Continue hyperlink. If it is not correct. 5. and that a Security Audit Trace has been activated for the SAPAG ID. On the Create Customer Messages screen. Database.sap. click the Service Connections button. Click the Choose button and you will be returned to the Customer messages – Create screen. On the Service Connections – Overview screen. click on the radio button to the left of the System type which has the problem: development system. if an add-on is not involved. From the expanded list of system. Click the Continue button. found in the SAP Note containing the advanced correction. set the days. select the appropriate SAP software release. On the next Customer messages – Create screen.. click on the radio button just left of the <SID> for which you are reporting the problem. click on the + sign next to Show systems to see a list of your SAP systems registered with SAP. Click on the red X in that instance’s line. select the appropriate priority of Low. If the problem involves an add-on. From the Component dropdown. 4. scroll down the page and find the SAP instance you want to open. or Very High. 1. click the Select a System button. test system. 3. 6. On the Customer messages – Create screen. scroll down to the bottom of the screen. Problem Logging with SAP Support Reporting a Problem to SAP 1. On the next Customer messages – Create screen. Before a Service Connection to a SAP server via your saprouter can be created. and Frontend dropdowns is correct.. or production system. 7. Return to Index.exe on your saprouter server before trying to add and open any Service Connections. select which SAP component is 2. Verify that the information showing in the Oper. System. In the Enter Data for the system’s semi-automatic opening popup.sap.

a secondary Component dropdown will appear. having the problem. scroll down to the bottom of the screen. After attaching all the necessary files. On the Spool Administration: Create Output Device screen. Return to Index. On the Spool Administration: List of Output Devices screen. When you have provided as much information as possible. 3... rename them all so that they have a suffix of “. Transporting.sap. 5. click the Close hyperlink to return to the Customer messages – Create screen. 3. You will receive an Output device was saved message in the status bar at the bottom of the screen. If there are logs or other files which might assist SAP in resolving the issue. 8. You may now leave the Message Wizard and close the web browser window. Creating. Make any changes that are unique for the new printer on the Device Attributes and Host Spool Acc Method tabs.. Once you select a component. Log on to any client in the appropriate SAP system. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. Go to transaction SPAD. Return to Index. 7. Do the best you can to make all three component pieces fit your problem as closely as possible. . 6. under the Devices/servers tab click the Output devices button. 11. 2. Click on a similar printer in the output devices screen then click the create with template picture-icon.. Log on to any client in the appropriate SAP system.com/message. Click on Customer Messages. Select a language from the Language dropdown.. You may now leave the SPAD transaction. Modifying. 12. All the open OSS problems you have sent to SAP will appear here. When all the required data has been changed/added. Deleting. click the Save picture-icon.. Click the lit match picture-icon to activate the printer. You may now leave the Message Wizard and close the web browser window. Select a secondary component and a third component as well. On the Spool Administration: Initial Screen screen.log” and use the Add attachment hyperlink and the Attachments popup to attach them to the message. Modifying a Print Device 1. Click the Continue hyperlink. fill in the Output device and Short name. click the pencil picture-icon to switch into change mode. You will receive a confirmation screen with a generation problem number. and type a more detailed description of your problem in the Long test box. Return to Index. Write this problem number down for later use. The easiest way to create a new printer is to copy an existing one. On the next Customer messages – Create screen. 2. Checking the Status of a Reported Problem 1. and Resetting Print Devices Creating a Print Device 1. type a short but descriptive summary of your problem in the Short description box. 9. 4. click the Send to SAP hyperlink. 10..

On the Spool Administration: List of Output Devices screen. Click on the output device to be deleted and then click the trash can picture-icon. On the Prompt for Workbench request popup. You may now leave the SPAD transaction.. 3. On the Spool Administration: Output Device (Change) screen. under the Devices/servers tab click the Output devices button. click the pencil picture-icon to switch into change mode. click the blank page picture-icon to create a new change request. You may now leave the SPAD transaction. You will receive an Output device deleted message in the status bar at the bottom of the screen.. click the green √ picture-icon. 2. Go to transaction SPAD.. Click the lit match picture-icon to activate the printer. under the Devices/servers tab click the Output devices button. Log on to any client in the appropriate SAP system. 8. You may now leave the SPAD transaction. under the Devices/servers tab click the Output devices button. 6. 6. On the Spool Administration: Initial Screen screen.. You will receive an Output device was saved message in the status bar at the bottom of the screen. On the Spool Administration: Initial Screen screen. 2.. 9. 2. click the Save picture-icon.. 5. 7. Deleting a Print Device 1. 6. You will receive an Entry is made in transport request message in the status bar at the bottom of the screen. 4. Return to Index. 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 pencil picture-icon to switch into change mode. Click on an output device to be transported and then click the truck picture-icon. 7.: Delete screen. Repeat steps 11 through 14 as many times as necessary.. Go to transaction SPAD. On the Spool Administration: Initial Screen screen. 4. Click the Yes button. 3. fill in the Short description and click the Save picture-icon. click the pencil picture-icon to switch into change mode. make any necessary changes on the Device Attributes and Host Spool Acc Method tabs. Log on to any client in the appropriate SAP system. Transporting a Printer or a Group of Printers 1. Go to transaction SPAD. On the Spool Administration: List of Output Devices (Change) popup. 3. verify that the correct printer is about to be deleted. 4. . When all the required data has been changed/added. Click the green √ to continue. Return to Index. Return to Index. 5. Double click on the output device to be changed. using the same transport request for all printers. On the Spool admin. On the Spool Administration: List of Output Devices screen. On the Spool Administration: List of Output Devices screen. 5. On the Create Request popup.

Log on to any client in the appropriate SAP system. On the same Administration: Output Device (Display) screen. 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. On the Spool Administration: List of Output Devices screen.. 3. 4. On the Administration: Output Device (Change) screen. This should at least narrow down the possibilities. . Go to transaction SPAD. On the Spool Administration: Output Device (Display) screen. 2. fill in the Output Name and Short name . Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. 8. 9. click the Change button and then the Create button. on the top-most menu bar click Edit → Reset Cache.. Word documents. 1. On the same Administration: Output Device (Display) screen. click the Output Devices button. 6. double click on the printer you need to reset. On the Spool Administration: Create Output Device screen. 6. etc without thinking about it. Return to Index. You probably do this all the time with Windows to printer spreadsheets.I normally use a short name of “DESK” for “Desktop Printing” but alot of people use a Short name “SWIN” or “LOCL” as well. As a rule. 3. 5. on the top-most menu bar click Edit → NI Reset. You can do the same thing using SAP. On the Spool Administration: List of Output Devices screen. On the Spool Administration: Initial Screen screen. 1. local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. 7. On the Spool Administration: Initial Screen. Go to transaction SPAD. try using some a non-SAP application to print to it to see if it working correctly on the network. Printer Output Creating a Local aka Frontend Printer aka Desktop Printer Local or frontend printing is sometimes confusing in concept but actually very easy to understand. under the Devices/servers tab click the Output devices button. click on the pencil pictureicon to switch from display mode to change mode. 2. You may now leave the SPAD transaction. You may now leave the SPAD transaction. 4. Resetting the Cache for a Printer If resetting the printer cache does not clear your printing problem. on the top-most menu bar click Edit → Reactivate. Log on to any client in the appropriate SAP system.. 5. That is _ _ D E F A U L T Save the printer.

. On the Output Controller: Spool request selection Screen screen.. Return to Index. Log on to any client in the appropriate SAP system. Log on to any client in the appropriate SAP system. On the Spool Administration: List of Output Devices screen. Go to transaction SP01. Re-routing Print to a Different Printer 1. click on the Output requests tab. Then click on the clock picture-icon. 3. under the Devices/servers tab click the Output devices button. 3. 4. Then click on the clock picture-icon. A list of all spool requests will be displayed. An Output request created message should appear in the bottom status bar. fill in any information needed to filter the selection results. . Return to Index. 2. You may now leave the SP01 transaction. A list of all spool requests will be displayed. 5.. Viewing a List of Pending Printer Output Requests for All Printers 1. On the Output Controller: Spool request selection Screen screen. A list of all pending output requests for the selected printer will be displayed.. On the Output controller: Print spool request XXXX screen. Click on the printer picture-icon. 6.. 2. Then click on the printer and page picture-icon. tab down to the line reading Output device and select a new printer. Click on the printer with a box outline picture-icon. Go to transaction SP01. Click on the printer picture-icon. You may now leave the SPAD transaction. Go to transaction SP01. Log on to any client in the appropriate SAP system. You may now leave the SP01 transaction. Double click on the spool request that is to be reprinted. 2.. Return to Index. Viewing a List of Output Requests for a Specific Printer 1. 4. Double click on the spool request that is to be reprinted. 5. Log on to any client in the appropriate SAP system. On the Spool Administration: Initial Screen screen. Go to transaction SPAD. 4. 3.. On the Output Controller: Output request selection Screen screen. Return to Index. A list of all pending output requests will be displayed. Reprinting a Document 1. click on the printer where you need to check the output requests. On the Output Controller: Spool request selection Screen screen. fill in any information needed to filter the selection results. 5. 3... Then click on the clock picture-icon. 6. 2. 5. fill in any information needed to filter the selection results. 4.

Administration of Temporary Sequential Data screen. On the TemSe --.Selection by software components of generation set section.. 7. 2. An Output request created message should appear in the bottom status bar. If a load regeneration jobs fails for some reason. Return to Index.. the BW users accessing reports via the internet use the . SAP IGS Server The IGS server (Internet Graphics Server) component displays and generates the graphics used by SAPGui HTML users. return to the SGEN screen for instructions on how to restart the job. On the Confirm redirection of output popup. click the All TemSe objects older than option to turn “on” the radio button to the left. 5. Go to transaction SGEN. 2. Go to transaction SP12. the status of mass generation is shown. After the successful deletion of the selected temporary objects. You may now leave the SP01 transaction.. On the SAP Load Generator screen – Select server for parallel generation section. On the Output control: Save attributes popup. Deleting Obsolete Temporary Objects and Reclaiming the Space 1. click the Yes button. on the top-most menu bar click TemSe database → Reorganization. On the TemSe --. 6. On the SAP Load Generator screen .. You may now leave the SGEN transaction and later return to check the progress of the recompilation. 3. click the Yes button. Click on the Continue button at the bottom. and “32” in production SAP systems. On the SAP Load Generator screen . 7. On the TemSe objects older than XX days popup. Click the Delete button. fill in the time and date listed under the Schedule job at button located at the bottom of the screen. Return to Index.. 5. Several messages will appear in the bottom status bar before the next screen appears. There is no task completion message. 8. click on the line reading Generate all objects in selected software components to turn “on” the radio button to the left. 4. Fill in the Days box with “7” for development and quality assurances SAP systems. Return to Index. On the SAP Load Generator – Job Monitor screen. For example. 3.Generation task section. you will be returned to the TemSe --. 6. Click the Continue button at the bottom of the screen. Click on the Schedule job at button. No other load regeneration jobs can be scheduled until this one completes. Click the button to the left of this entry.. Mass Recompilation of ABAP Programs 1. Log on to any client in the appropriate SAP system. click the button to the left of each entry listed in the Software component box. 7.Administration of Temporary Sequential Data screen. Log on to any client in the appropriate SAP system. You may now leave the SP12 transaction.Administration of Temporary Sequential Data popup. Click the Continue button at the bottom of the screen. click the Yes button. 4. there should only be one entry in the Server box. 6. On the SAP Load Generator – Job Monitor screen – Load generator status section..

4. 2.sap. while others like a permanent license key request or registeration of a new OSS ID. click on Maintain User Data → Request new users. The ITS server also channels graphics through the IGS server. You may log off the server. and the possibility of something being “wrong”. Return to Index.. language. You may now log off the SAP Marketplace. Stopping the IGS instance 4. department. Return to Index. language. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. can take 15 minutes. Requesting A New SAP Marketplace User ID aka “S” Number aka OSS ID 1. Then press Save.sap. 5.. department title. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service.com/user-admin. You may be asked for your OSS ID and password again. and email address of the person(s) being added as these are all required fields. 5. IGS server. Starting the IGS instance 1.. dependently on your point of original logon. 2. telephone number. .com/user-admin. Type the following: cd /usr/sap/<SID>/DVEBMGS00/igs¬ .. fill in the gathered information from step #1. You may log off the server. You will need the first and last name. Type the following: cd /usr/sap/<SID>/DVEBMGS00/igs¬ ./bin/stopigs¬ 6. 3. 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. On the User Data Maintenance screen. From the left navigational tree. The IGS server is installed as a started service on each server. you will learn the difference between normal lag time. or several days./bin/startigs -p . Log on to the appropriate server as <sid>adm. Log on to the appropriate server as <sid>adm. As you work with the various SAP provided tools. Checking A New SAP Marketplace User ID aka “S” Number aka OSS ID 1.. ¬ 3. function. You may or may not receive a confirmation message.

4. make sure you are at the same screen as in step #6 and click Save. say. you will see a list of your mostly recently generated OSS IDs. 3. The normal turnaround for an OSS ID generation is eight hours or less. On the User Data Maintenance screen. Modifying. 1. Return to Index. and you will be returned to step #6. click the Create Customer messages “on” box at the far left to the line. 6. 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. You may now log off the SAP Marketplace. If the Status reads Successful. From the left navigational tree. 3. If the Status reads “Requesting…”. you can fill in any of the information allowed in the top row to performa a search. From the second User Data Maintenance screen. On the User Data Maintenance screen. 5. 2. click “on” your option – Customer if you want the user to be able to open problems for any SAP Instance you own. and Deleting System Parameters Creating System Parameters .. When all the changes have been completed..com/user-admin. 9. click on the Surname of any user you wish to change. click Search for an entire list of your SAP Marketplace users. please open an OSS problem to get it resolved. 2. 7. dependently on your point of original logon. Repeat as many times as you need to do so in order to change the OSS ID to your requirements. your OSS ID has not been generated so come again later to check the status. 5. 8.. Creating. click on a line you want to change. click on the Authorizations tab. if you want the OSS ID to be able to create new OSS problems with SAP. You may be asked for your OSS ID and password again. click on Maintain User Data → Search and maintain users. click on Maintain User Data → Display requested users. Return to Index. On the resulting User Data Maintenance Create Customer messages screen. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. Verify the status of the OSS ID for which you are looking. On the next User Data Maintenance screen. If the Status makes reference to some type of error condition. From the resulting User Data Maintenance Authorization objects overview screen. or fill in the provided fields to help narrow your search.. From the left navigational tree. and then click the Edit button on the bottom of the displayed section. 10. and both the User ID and Initial Password fields contain legitmate data. pressing Search when you are ready. or select a specific Installation(s) for only. You may be asked for your OSS ID and password again.sap. CRM instances. your OSS ID has been generated and you can pass the information on to your user. You may now log off the SAP Marketplace.. You should get a screen thanking you and saying that your changes have been saved. For example. dependently on your point of original logon. 4. Click the Add button at the bottom of th page. If the user ID you are seeking does not appear on the screen.

Click the white arrow on green picture-icon. Deleting System Parameters 1. On the Edit Profiles screen. On the Maintain R/3 Profile screen. 7.. On the Maintain R/3 Profile screen. 16. click the No button. On the Edit Profiles screen. 18. On the Activate profile popup. On the Edit Profiles screen. In the Edit profile section. Log on to any client in the appropriate SAP system. 4. 11. Log on to any client in the appropriate SAP system. click the radio button to the left of Extended maintenance. You will not get a confirmation message. Click the white arrow on green picture-icon twice. Go to transaction RZ10. 11. Click the Change button. Click the Change button. Click the Copy button. click the green √ button. On the Edit Profiles screen. click the Yes button to save your changes.. type in the new Parameter name and Parameter val. 13. Modifying System Parameters 1. 9. .. You will not get a confirmation message. You may now leave the RZ10 transaction. 17. 14. click the green √ button. click Parameter → Delete. 4. Go to transaction RZ10. 6. click the Save picture-icon. Return to Index.. click the green √ button. On the Save profile popup. Log on to any client in the appropriate SAP system. On the Edit Profiles popup. If you receive a Possible Inconsistencies in OP Modes screen. click the Save picture-icon. On the Edit Profiles popup. select the <SID>_DVEBMGS00_SAP<SID> Profile from the dropdown. On the Save profile popup. You may now leave the RZ10 transaction. If you receive a Possible Inconsistencies in OP Modes screen. 2. double click over the <No> unless you are unsure of why this message has been displayed. locate the parameter that needs to be changed in the Parameter name column. 6. double click over the <No> unless you are unsure of why this message has been displayed. click the Yes button.. select the <SID>_DVEBMGS00_SAP<SID> Profile from the dropdown. On the Caution! Caution! Caution! popup. Go to transaction RZ10. click the No button. click the radio button to the left of Extended maintenance. 9. or whatever instance profile you need to change. On the Activate profile popup. 3. or whatever instance profile you need to change. 15. Return to Index. On the top-most menu bar. locate the parameter you need to delete and click on the Parameter name to high-bright it. or whatever instance profile you need to change. 10. In the Edit profile section. On the next Maintain R/3 Profile screen. Click the Change button. In the Edit profile section. 12. click the Yes button. 3. On the Maintain R/3 Profile popup. 8. 7. Click the Copy button. select the <SID>_DVEBMGS00_SAP<SID> Profile from the dropdown. On the Edit Profiles screen. On the Caution! Caution! Caution! popup. 10. Change the matching value under Parameter value to the new value. On the Maintain R/3 Profile screen. click the radio button to the left of Extended maintenance. click the green √ button. 2. 5. 8. click the Add Parameter button.

You may now leave the SM50 transaction. 11. click the Yes button. Return to Index. click the green √ button. 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. Click on any process thread and then click the blue cylinder with glasses picture-icon. Go to transaction SM50. On the Edit Profiles popup. If a thread is being used. 2. click the Process → Cancel without core. Return to Index.. On the Edit Profiles screen.. the client in which the report is running. On the Caution! Caution! Caution! popup. the name of the report running will be displayed as well as the number of seconds that the report has been running.. Use the white arrow on green picture-icon to go back to the Process Overview screen. find the process which must be stopped. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display. 8. the table the report is currently accessing. Click on the blue arrow circle picture-icon to refresh the process data appearing on the screen. Click the Copy button. 1. 6. if applicable. Click the Yes button to delete the parameter. click the green √ button. You may now leave the SM50 transaction. 5. 9. On the Process Overview screen. all processing threads for the SAP system are displayed. 6. On the Process Overview screen. 5. 3. click the Save picture-icon. double click over the <No> unless you are unsure of why this message has been displayed. On the Save profile popup. 12. You may now leave the RZ10 transaction. You will receive a Parameter was deleted message in the status bar at the bottom of the screen. Log on to any client in the appropriate SAP system. 3. On the Activate profile popup. If you receive a Possible Inconsistencies in OP Modes screen. . the operating system. 4. 4. Use the white arrow on green picture-icon to go back to the Process Overview screen. Place a √ in the □ to the left of the process number to be stopped by pressing Space. This information is useful when tracking process thread problems. On the next Maintain R/3 Profile popup.. This will display the Trace Data screen which shows the actual communication between SAP. This information includes database access statistics and timings. Go to transaction SM50. 7.. the action the report is currently doing. On the top-most menu bar. 8. 7. and. 4. Click the white arrow on green picture-icon. Overview of All Work Processes Running on a SAP System 1. click the No button. 10. Stopping Run-Away or “Bad” Work Processes Log on to any client in the appropriate SAP system. and the database server. make sure that the parameter listed is the one you need to delete. 2.

You may now leave the RZ10 transaction. If you want to limit the message to one client. On the Save profile popup. On the Maintain R/3 Profile screen. type up to 3 lines of System message text. or whatever instance profile you need to change. 12. Log on to any client in the appropriate SAP system. 4. Return to Index. If this does not kill the session. 2. 3. On the Edit Profiles screen.. click the No button. 6. On the Create System Messages popup. you have no choice but to “bounce” the SAP instance and/or possibly the serve. 5. On the Caution! Caution! Caution! popup. Log on to any client in the appropriate SAP system. In the Edit profile section. you can log on to the server.. 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. 3. 2.exe. 7.. Go to transaction RZ10... click the Save picture-icon. select the <SID>_DVEBMGS00_SAP<SID> Profile from the dropdown. there is an executable in the RUN directory on the server called sapntkill. 2. On the Edit Profiles popup. Increasing or Decreasing the Number of Work Processes 1. Change the matching value under Parameter value to the new value. On the Activate profile popup. rdisp/wp_no_btc. open a Task Manager session. Do the same for the batch processes. click the No button. Select a server (there should only be one) from the Server dropdown. On the Edit Profiles screen. Return to Index. Click the Copy button. you can go to transaction SM04 and kill the user’s session. You may now leave the SM02 transaction. 11. Log on to any client in the appropriate SAP system. Click the Change button. locate the dialog processes rdisp/wp_no_dia line in the Parameter name column. If this does not kill the process. When all the changes have been made. click the green √ button. 5. Click the green √ to save the message. If none of the above work. click the Yes button. Go to transaction SM02. click the white arrow on green picture-icon. 4. Broadcasting System Messages Creating a System Message 1. On the Save profile popup. click the green √ button. and End the Process.. 8. Go to transaction SM02. Return to Index. Be sure to click the Copy button after each change. 10. If this does not kill the process. click the radio button to the left of Extended maintenance. Run it providing the process ID number. fill in an Expiry date and/or Delete date. click the Create button. . rdisp/wp_no_vb. On the System Messages screen.. and the update processes. Modifying a System Message 1. 9. A System message added message will appear in the bottom status bar. If desired. select a client from the Client dropdown. You will not get a confirmation message.

Short Dump Analysis Short dumps care generated when one of the SAP programs encounters an “abnormal” condition.. Log on to any client in the appropriate SAP system. 3.. You may now leave the SE37 transaction.. The transaction is now locked. click the Yes button to delete the message. Go to transaction SM02. type in the Function name “TH_POPUP”. Go to transaction SM01. 3.. On the Function Builder: Initial Screen screen. While it is not a function of the Basis support team to “debug” SAP programs. 6. On the Transaction Code: Lock/Unlock screen. The message will be sent to the specified user. A System message changed message will appear in the bottom status bar. Click the clock picture-icon. 3. 2.. A System message deleted message will appear in the bottom status bar. Locking R/3 Transactions 1. You may now leave the SM02 transaction. click the pencil and glasses picture-icon to switch to change mode. 4. Deleting a System Message 1. Click the Single Test wrench picture-icon. 2. On the Change System Messages popup.. Return to Index. 4. 2. Return to Index. 4. Type in the transaction code you want to lock and press Enter. Client. You may now leave the SM01 transaction. Log on to any client in the appropriate SAP system. On the Display System Messages popup. 3. On the System Messages screen. You may now leave the SM02 transaction. click on the Id number of the message to highlight the message that needs to be deleted. Place a √ in the □ to the left of the transaction to be locked by pressing Space. double click on the Id number of the message that needs to be changed. On the System Messages screen.. 5. fill in User.. 4. Go to transaction SE37. Return to Index. Sending a System Message to a Single User 1. Log on to any client in the appropriate SAP system. The transaction code to be locked should appear at the top of the transaction list. Click the Delete button. 5. and Message Text. 5. On the Test Function Module: Initial Screen screen. familiarity with . Return to Index.. 5. a condition that the program was not coded to handle in any of its error routines. you will see an empty box at the very bottom of the screen. make your changes and click the green to save the changed message. Press Enter. On the System message: Delete popup.

the Yesterday button for yesterday’s dumps. When this happens. Any other transactions attempting an update on the “locked” object fail. you can use the Refresh button to monitor the table locks. Click the List button. Return to Index. any unique information in the Error analysis section. some of the dump sections can be valuable for SAP Note searches and/or logging system problems with SAP. an update transaction fails. 3. 2. Log on to any client in the appropriate SAP system. and the update fails. or double-click any line for detail information. You can also use this transaction to delete a table lock or all table locks.. On the List of Selected Runtime Errors screen. 4.. Viewing Database Lock Information 1. appear in the system log. On the Runtime Error Long List screen. You may now leave the SM12 transaction. Log on to any client in the appropriate SAP system. 5. To remove these update locks. locks placed on resources may not be released. Go to transaction SM12. Return to Index. On the Lock Entry List screen. You may now leave the ST22 transaction. You may now leave the DB01 transaction. fill in the Table name or use *. Viewing Table Lock Information 1. If the update cannot be forced to completion. The information displayed on the Oracle Lock Monitor screen can be sorted and filtered to meet your reporting requirements. 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.. the Client or use *. the lock should be removed from the object. and search terms for searching SAP Notes in the How to correct the error section. 4. On the ABAP runtime errors screen. 3. 3. double-click on any short dump you want to examine more closely. Go to transaction ST22. Database errors. 2. if necessary.. and the User name or use *. 6. . the lock may still be present in the SAP system.. you can click the Today button for today’s dumps. Log on to any client in the appropriate SAP system. Return to Index. due to a dropped user session or some other unknown reason... On the Select Lock Entries screen. 1. Viewing Update Lock Information Occasionally. including SAPSQL_ARRAY_INSERT_DUPREC errors. If an object was marked as currently being updated. Go to transaction DB01. 2. you should try to force the update to complete. 5. 4. make note of the error that occurred in the What Happened? section.

Click on the Perform Post Installation Actions button. If this is the case. skip to step 7. use the following section Adding New Instance to TMS Setup. . 4. Log on to client 000 of the SAP instance to serve as the Domain Controller. If. Return to Index. The best way to resolve incomplete update records is to try to force them to completion. On the Update Records: Main Menu screen. so don’t worry about being too specific. You will be given an opportunity to change your selection criteria in the Delete Update Records popup. 7. go back to the previous screen and open your search by using “*” in client and user. Return to Index. press Enter. click Update records → Update → All records.. do not use this section to add a new instance to the existing TMS configuration. If the list is empty. But if the originating lock happened some time ago. forcing the update may not be an option. Go to transaction STMS. You may now leave the SM13 transaction. 4.Transport Management System . after reading this information message. Click the green √ picture-icon to continue.. From the top-most menu of the Update Records screen. Directories can be sorted by Name or Date/Timestamp. 6. 1. If you still get no results. Viewing OS Server Files from SAP The SAP directory structure on a Linux server can be viewed via SAP using the AL11 transaction. 2. click Update records → Delete → All records. When you have entered all your information. 5. using a date range will not help. Using a From date and To date range can help as well. You will not receive a confirmation message after the update or delete. and a date range of 01-01-2000 through 12-31-2010. 1. 3. If the update records are fairly old (a day or so) and/or the update force produces an error. You will be given one last chance to stop via a Update selected records popup. Go to transaction SM13. making them untransportable. From the top-most menu of the Update Records screen.. You could severely damage any pre-existing transports. if you are looking for the update locks produced by a specific user and/or in a specific client.. Transport Tasks Configuring TMS . there aren’t that many “hanging” update locks at one time. You will be given one last chance to stop via a Delete data will be lost popup. Go to transaction SE06. deleting the update lock is probably your best course of action. You will see an Update – Updating update requests which have not yet executed popup. Click Yes to start the delete. 8. there are no incomplete update records. 3. Log on to any client in the appropriate SAP system. 2. click the green √ picture-icon. Normally..for the First Time Note: if you already have a TMS configured. Otherwise. The Update Records screen contains a list of outstanding update records matching your selection criteria. All the usual SAP directories are accessible as well as any custom data views. Instead. or you are unsure whether forcing the update record to completion is the wisest choice. you decide that deleting the update records would be a wiser decision. Click Yes to start the update. type in the Client and/or User. Text files can be accessed and ported in and out of the SAP instance.

19. Click on the Perform Post Installation Actions button. Return to Index. Save your way back the the main STMS screen. On the Change Transport Routes screen. If the popup doesn't say that. 6. On the Display Transport Routes screen. Go to transaction SE06. click Configuration → Standard Configuration → Development and Production System. click the Display<>Change button to toggle into Change Mode. or make up a <SID> if you are never really going to have another SAP system. and the description of the Transport Domain. On the Display Transport Routes screen. Log on to client 000 in the SAP instance you want to add to the existing TMS Domain. back out until you are). back out until you can once more see the Transport Management System screen. and click the √ Continue button. Click the Save button. click the User Settings button.. 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. Fill in the Development and Production System popup.. 5. click the Save icon and confirm all the popup questions. On the Transport Management System screen (if you aren’t there. Use the dropdown to find the correct entry it the field is blank. Click Overview → Systems. Do step #16 for every system in your TMS Domain. Adding a New SAP Instance to an Existing TMS Domain Controller 1. . You should see a popup box with the title TMS: Configure Transport Domain. 4. Fill in the rest of the information including the Path which is assumed to be \\<current server>:\usr\sap\trans for NT or /usr/sap/trans for UNIX. 15. 12. Add a Parameter of CTC and a Value of 1. 16. Go to transaction STMS. 17. 18. On the System Overview – Domain Domain_<SID> screen. You may now leave STMS. Back out of the screen and then go back in – you should see the list in a text mode which makes it easier to handle. Click the √ mark to Continue. assuming that this is the first SAP instance and there are no other installed SAP instances in your landscape yet. 10. Then click Save. Click the Communication tab and make sure that the Transport Group Name is correct.. 3. On the Change Transport Routes screen. click on Overview → Systems. using your current SAP system SID as the Development system and the SAP instance you created in step #8 as the Production system. 13. Verify that the information on the tab is correct and click the Insert Row button. double-click the TMS Domain domain controller SAP instance. Click Environment → Transport Routes. It should contain of the Domain Controller in the format of DOMAIN_<SID> where <SID> is the System ID of the SAP Domain controller. and assuming that you want your transport requests to be transportable and not local only. 8. On the Display TMS Configuration: System XXX screen. 14. Back on the Change Transport Routes screen. press F6 to change to the correct popup box. Fill in the TMS: Configure Transport Domain popup with the Description. click SAP System → Create → External System. click the Display<>Change button to toggle into Change Mode. 7. 11. 2. Name of DOMAIN_<SID>. making sure to change all Transport Group Names are the same and the CTC row is added to each with a value of 1. 9. Click the Transport Tool tab. On the Display TMS Configuration: System XXX screen. turn “on” the Hiergraphical List Editor.

9.. 12. Highlight the System you just added and then click SAP System → Approve. you can go to /usr/sap/trans on the OS level and in directory cofiles copy K00050. etc. Log on to client 000 of the Transport Domain Controller and go to transaction STMS. On the Select Request Type popup. use the Consolidation boxes to enter the SID of the transport domain. You will get a new transport request number.. 14. Make sure that the Transport Group name is the name of the original transport domain. Click the Save. 8. Make sure that the Released check box is "on" in the Request Status section and click the Execute icon. Verify that the information on the tab is correct and click the Insert Row button. You should see a message that says SAP System waiting to be included in the Transport Domain. Back out to the main Transport Management Screen. On the Display Transport Routes screen. 3. mistakes just happen. On the Enter Transport Request popup. and System number of the TMS Domain Controller then click Save. Back on the Transport Management System screen. Fill in the TMS: Include System in Transport Domain popup with the Description. 4. Back on the Transport Management System screen. On the Create Transport Route popup. Make a Local Transport into a Transportable Transport Sometimes. click "on" radio buttion Workbench Request. Once it is released. Add a Parameter of CTC and a Value of 1. 7. and confirm that the SAP System waiting to be included in the Transport Domain has disappeard. This new request can be released using one of the transport organizer Transactions like SE10. 6. 13. we will use a transport SM1K00047 as the erroneous change request. put SM1K00046 in the first Request/Task field. keeping your original session in the other SAP instance open. Press F6 until you see a TMS: Include System in Transport Domain popup. On the Merge Objects List screen. For this example. 11. Double-click on the new system..SM1 to K00046. 1. click on the Merge icon. √ icon. 7. You can switch back to the new instance. On the Merge Objects List screen. 11. and the SID of the system you are adding. Click the Transport Tool tab. Return to Index. etc. click Environment → Transport Routes. fill in the necessary information and make sure that the fill in the Target field so that the transport request is NOT local. On the Transport Management System screen. in our case SM1K00050.SM1. click Overview → Systems. Click Save and confirm. 10. Click the Save button. until everything is done. and in directory data copy . 2. Click on Edit → Transport Route → Create. 5. click the Create Request icon. On the Create Request popup. On the Transport Organizer List screen. Make sure to release SM1K00047 before beginning this procedure. create a Z* transport layer. Then confirm all the messages. click Overview → Systems. click on Merge Object Lists which is in the Requests/Tasks section. OK. click the Display<>Change button to toggle into Change Mode. Go to SE03. 6. Log on to the client who is the owner of the local transports that needs fixed. 5. Target Host. change it. You should see a popup box with the title TMS: Configure Transport Domain. If not. 3. and click on the Communications tab. You may now log out of both SAP instances.

The transport request should now appear at the bottom of the queue list.. Click Request → Import.. 4. 2. Make sure that the first three options are checked "on" in the Options tab. highlight all the transactions you want to manually transport... Return to Index. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions. Double-click the queue for which you want to view the history. Transporting Change Requests To manually transport change requests from DEV/QAS to PRD: 1. Make sure the change request(s) you want to transport shows in the queue.SM1. 3. click on the green √ and confirm the next popup. Leave the change requests highlighted. 4. Adding a Change Request to a Transport Queue 1. Go to transaction STMS and click Overview → Imports. Click on Extras → Activate Inactive Requests. 6. It shoud have been updated automatically.. Viewing the Transport Queue History 1.. 8. Make sure that Synchronous radio button is "on" in the Execution tab. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions. Fill in the Number of the Transport Request to be added to the queue and then press Enter.. Go to transaction STMS and click Overview → Imports. 2.. Return to Index. Once you have control of your session again. the transports are done. Click on Extras → Other Requests → Add. 5. This bypasses the STMS_QA process. Verify their return code in the Import Queue list. Using the F9 button. Go to transaction STMS and click Overview → Imports. Re-Transport Several Change Requests at Once 1. Verify their return code in the Import Queue list. Once you have control of your session again. Confirm the Add Transport Request popup.and click the Import History button or press Ctrl+F7. 3. When you are done. R00050. On the popup. Click on the Import History button or press Ctrl+F7. Return to Index. Highlight the queue into which the transport(s) to be moved again were originally transported – the “FROM” queue . make sure that the target is client 300. Confirm the popup. The resulting list can be sorted and filtered to produce a more exacting report if needed. Double-click the PRD queue. Click the refresh button to make sure you have the most current view of the PRD queue. 2. the transports are done..SM1 to R00046. Go to transaction STMS and click Overview → Imports. You may now leave SE03. It shoud have been updated automatically. Return to Index. Double-click the PRD queue. .

9. Back on the Change Transport Routes screen. and b) be the target of a consolidation route. 3. 5. 6. Use Target Groups to Transport to Mulitple Clients in Two Different Instances 1. You may get a message asking if you want to check the the transport tool for all systems. 3. On the Transport System Management screen. Go to transaction STMS.. we will DEV 100. In the Create Transport Group popup. On the Import Overview screen.. give a Short Description and click the Client Assignment button. Use the F9 to select and/or unselect as many as you need to transport. click Overview -> Transport Routes. click Request → Forward → System. Confirm the Disturbution of it to the other SAP Instances. 10. You now have a Transport Group. 7. If you see any thing but red green Oks. Click on the Target Groups line and click the Create button. In the Create Transport Route popup. Now you must create a Consolidation Layer. You now have a target group.. click on Transport Routes and click Create. Log on to client 000 of your TMS Domain Controller SAP Instance. 4. Once all choices have been made. Click the green check mark to Transfer. Now you can go to the “TO” queue and refresh the list. Be aware that the Target Group name must start and end with a “/”. On the TMS: Check Transport Tool screen. Return to Index. If only want to check a limited subset of the SAP instances. 4.. QAS 200.. 2. click Import Queue → Check → Transport Tool. Transport Tool System Confirmation 1. Fill in the “TO” system and click on the Execute green √ mark. 2. click the Extended Transport Control button at the bottom of the popup. Your imports should all be there. Correct these problems and then run this report again until it comes back clean. . expand all the lines with the non-OK marks and look for more information. use F9 to select and/or deselect those systems before you click Transport Tool. fill in the Target Group as /XXXCLNTS/. Return to Index. Enter each Target system and Target client you need. a list of all selected SAP instances to be checked will appear. If your SAP instance is older.. and QAS 210. 3. Make sure Consolidation is "on" and fill in the information using our Target Group as the Consolidation Target. For our example. Click the green check button to Save the change. 2. 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. 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. See topic Using Target Groups to Transport to Mulitple Clients in Two Different Instances to fulfill the a) requirement. On the Display Transport Routes screen. Go to transaction STMS and click Overview → Imports. Return to Index.. click the Display<>Change button to toggle into Change mode. 8.

6. give a Short Description and click the Client Assignment button. Click "on" Quality Assurance .. Enter each Target system and Target client you need. If you ever need to change this job. Although Period appears grayed out. Click on the instance in which you want to control QA. Make sure "At Start Time" is on. 8. Now you must create a Consolidation Layer. You now have a target group. fill in the Target Group as /XXXCLNTS/. 6. Log on to client 000 of your TMS Domain Controller SAP Instance. click on Transport Routes and click Create.. Back on the Change Transport Routes screen. you can still change it to the periodic value you need. On the Import Queue screen. click the Refresh button. Double-click on the queue for the SAP instance are in. fill in the information for the job. 5. click the Extended Transport Control button at the bottom of the popup. and once an evening in PRD. 7. I recommend every hour in DEV. Log on to client 000 of your TMS Domain Controller SAP Instance. 1. Confirm the Disturbution of it to the other SAP Instances. Click the green check to Transfer your changes. Go to transaction STMS. click on the Target Groups line and click the Create button. In the Create Transport Group popup. You may now leave the STMS transaction. Automate the Transport Process 1. Then back out. click Display<>Change button to toggle into change mode. Now you have met condition a. Return to Index. 9. this is QAS and the instance to be controlled is PRD. Go to transaction STMS. click Overview -> Transport Routes. 3. Click the green check button to Save the change. On the Create Transport Route screen. 10. In the Create Transport Route popup. Be aware that the Target Group name must start and end with a “/”. 4. Click the green check mark to save. 2. click the Procedure button and make your changes. Make sure Consolidation is "on" and fill in the information using our Target Group as the Consolidation Target. 4 times a day in QAS. On the Transport System Management screen.. 4. Click on the green check mark to Continue. make sure Delivery is "on" and fill in Source and Delivery systems with QAS and PRD. Return to Index. You now have a Transport Group.. 3. 2. 11. Click on the Import All Requests button. click on the QAS instance and click Create. click Overview -> Imports. Click the green check mark to Transfer. 12. User Tasks . Under Transport Routes. You will see a Change System Attributes popup. you must do it via STMS and not SE37. Back on the Change Transport Routes screen. You may now leave the STMS transactions.. Back on the Change Transport Routes screen. click on the QAS instance and click the single pencil Change button. If you want to change the people who OK the transports. On the Transport System Management screen.Delvery After Confirmation. 5. Normally. On the Start Import popup. On the Display Transport Routes screen.

You may now leave the SU01 transaction. On the User Maintenance: Initial Screen screen. Return to Index. Go to transaction SU01.. You may now leave the SU01 transaction. Log on to the appropriate SAP system and the client where the new user is to be added. Go to transaction SU01. Go to transaction SU01. You will receive a User saved message in the status bar at the bottom of the screen.. Return to Index.. 4.. On the User Maintenance: Initial Screen screen. 2. Creating. type in the User name to be copied and click the double blank page picture-icon. 6. type in the new User name and click the blank page picture-icon. Internet mail Initial password. repeat password. user type Decimal formation. Copy an Existing User to a New User 1. First name. Deleting a User 1. Go to transaction SU01. 3. . 4. You will receive a User saved message in the status bar at the bottom of the screen. Return to Index. When you are done. On the Maintain User screen. Log on to the appropriate SAP system and the client where the user is to be changed. You will receive a User saved message in the status bar at the bottom of the screen. 8. 5. and Deleting Users Creating a User 1. When you are done. 3. 2. On the Maintain User screen. type in the user’s name and click the pencil picture-icon. type in the To for the new user and click the Copy button. On the User Maintenance: Initial Screen screen. Date formation. click the Save picture-icon. Modifying a User 7. 9. You may now leave the SU01 transaction. 2. Time zone. click on the tabs and make your user information changes. When all necessary data has been entered. On the Copy User popup. 10. On the Maintain User screen. fill in at least the following information for each tab: Address Logon data Defaults Roles Profiles Last name. click on the tabs and make the changes to the user’s information. Log on to the appropriate SAP system and the client where the user is to be deleted. click the Save picture-icon. 11. click the Save picture-icon... Log on to the appropriate SAP system and the client where the user is to be changed.. OutputDevice Select roles to be added to the user Select profiles to be added to the user 5. Modifying.

Modifying a User’s Password 1. On the User Maintenance: Initial Screen screen. Click the Save button. Go to transaction SU01. and when done press Enter. type in the user’s name and click the lock/unlock picture-icon. 4. 4. On the Change Password popup. type in the user’s name and click the trash can picture-icon. Return to Index. 5.. On the Change Roles screen. Fill in the name(s) in the field(s) provided.. You will receive a User locked message in the status bar at the bottom of the screen. 5. 5. enter the new password in both the New password and Repeat password boxes. Click the Change role little yellow pencil button. On the User Maintenance: Initial Screen screen. On the Lock user popup. Once the comparision is done. 3. On the User Maintenance: Initial Screen screen. 2. Log on to the appropriate SAP system and the client where the user is to be locked. You may now leave transaction SU01. Click the Change button or press Shift+F6. and on the Role Maintenance screen. On the User Maintenance: Initial Screen screen. 3.. 4.. Click on User Comparison and then Complete Comparison. Go to transaction PFCG.. You may now leave the SU01 transaction. click the User tab. 6. Go to transaction SU01. 2. Return to Index. click Save one more time and you are done! Return to Index. click the lock picture-icon.. Click the green √ picture-icon... Return to Index. Log on to the appropriate SAP system and the client where the user’s password is to be changes. Log on to the appropriate SAP system and the client where the user needs the role. 7. On the Maintain User screen. . Locking a User 1. You will receive a The password was changed message in the status bar at the bottom of the screen. Go to transaction SU01. click on the Roles tab. You will receive a User deleted message in the status bar at the bottom of the screen. type in the user’s name and click the lock/unlock picture-icon. You may now leave the SU01 transaction. Add a Role to a User 1. click the Yes button. type in the name of the role to which the users where added and press Enter to confirm exist of the role. On the Delete user popup. 3. 2. 5. 8.. 4. type in the user’s name and press Enter to confirm that the user exists. 3.

each SU10 batch run must use all Adds or all Removes but never a mixture. 7. City. however. Back on the Maintenance: Mass Changes Initial Screen screen. 6. Reference User. 3. Once all your changes have been made. Extension. Do all Adds in one run and then all Removes in another. User ID. 8. Go to transaction SU10. 2. Save the changed users. User Information Repository Reports 1. On the User Information System screen. Please note. 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. Department. Company. changing data and clicking the Add or Remove button for each correction. 4. Go to transaction SUIM. you can click “on” the users to be changed. To make the changes. Once all the users you want to change have been selected.. Return to Index. On the Users by Complex Selection Criteria screen. Room. SAP has provided mass change transaction to help eleviate the tediousness of making many user changes. Log on to the appropriate SAP system and client where the user reports are to be generated. On the User Maintenance: Mass Changes Initial Screen screen. fill in the fields you want to search on in the Users by Complex Selection Criteria screen. you can print it or send it to your hard disk. It should be noted. and Cost Center. Once you have all the users selected that you want to change. click the Save button. If you click Address Data. Expand the list to see the transactional details. you need to select whether you will select users based on Address Data or Authorization Data and click the appropriate button. you need to add a new role to and delete an existing role from 20 users. Last name. For either method. Click on the clock picture-icon to the left of the report you want to run.. you will see how many users you are about to change. You may now leave the SU10 transaction. On the Log Display screen. On the Mass changes popup. and many other fields. Mass User Changes Making user changes one-at-a-time can be extremely time consuming not to mention boring. Also note that it is best to make one type of mass change at a time. 5. click on Yes.. Then delete the existing role from the same 20 users. Return to Index. 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. and click the Execute button. you can find users with any combination of First name. you cannot change the password for multiple users. Athorization Objects. 4. that the mass change transaction is limited as to the changes that can be made. 3. scroll through the tabs.. 5. you can specify a combination of Groups. For example. Once your report has been produced. 1. Building. 9. The best method to achieve this would be to first do a mass change to add the new role. Log on to the appropriate SAP system and the client where the user changes are to take place. you will see a log of the changes you made. On the Mass User Changes screen. or click the Select All button. . You will be taken to a selection filter screen to customize the data you need to see on your report. click the Transfer button. Authorizations. For example. click User → Change. If you opt to use Authorization Data.. You may now leave the SU01 transaction. 2.

4. 2.. Log on to the appropriate SAP system and client where the user reports are to be generated. You may now leave the SU01 transaction. You will be taken to a selection filter screen to customize the data you need to see on your report. You may now leave the SM19 transaction. Return to Index. On the Overview of Sessions popup. Click the End Session button. 2. all users currently logged on to the SAP system are displayed. Once you have entered all your trace information. you can print it or send it to your hard disk. You will not receive a deletion confirmation message. 7. 5. From the top-most menu bar on the Security Audit: Administer Audit Profile screen. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen. On the Create new profile popup. 6. Go to transaction SM19. Click on the clock picture-icon to the left of the report you want to run.. On the User Maintenance: Initial Screen screen. 3. Log on to any client in the appropriate SAP system. 5. select the Clients and User names to be traced. In the Selection criteria section. Please note that while the user trace has been saved. 4. On the User List screen. click “on” all the auditing functions you need for this profile. Tracing a User’s Activity Creating a User Audit Profile 1. Once your report has been produced. see the next section Activating a User Audit Profile. 10. 3... click the □ to the left of Filter active to place a √ in the box. . it is not yet active. click Profile → Create. from the top-most menu bar click Information → Information system. Log on to any client in the appropriate SAP system. Displaying and Dropping User Sessions 1.. To activate the user trace. 9. User Information Repository Reports 6. You will receive an Audit profile saved in the status bar at the bottom of the screen. 8. In the Events section. Return to Index. 11.. click the Save picture-icon. place a √ in the □ to the left of the user to be dropped and click the Sessions button. type in a new Profile name and click the green √ pictureicon. 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 the radio button to the left of the level of auditing you need. You may now leave the SM04 transaction. Go to transaction SU01. In the Audit classes section. Return to Index. On the User Information System screen. 7. To delete a user’s session. Go to transaction SM04. click on the session No to be deleted.

Return to Index. Click the trash can picture-icon.. Log on to any client in the appropriate SAP system. 2. Log on to any client in the appropriate SAP system. select the audit profile to be activated from the Profile dropdown. 3. You may now leave the SM20 transaction. Audit classes. Return to Index. You may now leave the SM19 transaction.. click the Yes button. Return to Index. You may now leave the SM19 transaction. click the Profile → Deactivate. 2.... The audit will not begin until after the SAP instance has been recycled.. select the audit profile to be deactivated from the Profile dropdown. You will receive an Audit profile activated for next system start in the status bar at the bottom of the screen. Security Tasks . On the Security Audit: Administer Audit Profile screen. 4. On the Security Audit: Administer Audit Profile screen. provide your information to filter the audit information. From the top-most menu bar. Go to transaction SM20. 3. be sure to include that user’s ID. Return to Index. You may now leave the SM19 transaction. and Events to select sections of the Security Audit Log: Local Analysis screen. On the Security Audit: Administer Audit Profile screen. In the Selection. Go to transaction SM19. 2. Deactivating a User Audit Profile 1. Activating a User Audit Profile 1. You will receive an Audit profile deleted in the status bar at the bottom of the screen.. 3. 4. Log on to any client in the appropriate SAP system.. 5. Go to transaction SM19. 4. 3.. Viewing the Audit Analysis Report 1. On the Confirmation prompt popup. You will receive a Current audit profile was deactivated in the status bar at the bottom of the screen. This list can be printed using the usual methods. Log on to any client in the appropriate SAP system. 5. 2. If you need to trace the activities of a specific user. Go to transaction SM19. Click the lit match picture-icon to activate it. Click the Re-read audit log button. 4. select the audit profile to be deleted from the Profile dropdown. The resulting list is displayed. Deleting a User Audit Profile 1.

expand and change the authorizations you need to adjust.TCODE = AGR_TCODES.. On the Role Maintenance screen. 5. either one of your own or one of the ones provided to you in the installation of SAP. If you want to only select specific roles from a Composite role. AGR_TCODES. Log on to client needing the role change. you will be taken back to the original PFCG screen where you will see the name of your new role. Go to transaction PFCG.AGR_NAME AND TSTCT. Come up with a standard that everyone follows so the base original role is designated in some way so you don’t forget where you got the original. Role Description. Click the Change Role little yellow pencil button role button or press F6. 4. TSTCT WHERE AGR_TEXTS.. 6.SPRAS = 'E' AND AGR_TEXTS. 1. Creating a User Role The easiest way to create a new user role is to copy an already existing user role. Go to transaction PFCG. you would click the Copy selectively button. The name must begin with Z or Y. fill in the to role field with the name to be given the new role. 2. either type in the role name to be copied or select it from a dropdown. Transactions contained in the Role.TTEXT FROM AGR_TEXTS. Press Enter to confirm that the role exists. When finished click first the Save button and then the Generate button – looks like a little red and white beachball. click Save one more time and you are done! Return to Index. On the Change Role: Authorizations screen. 7. AGR_TCODES. and the Transaction description. 3. It might assist you with picking one of these roles if you have someone dump the appropriate information into a spreadsheet containing the Role Name. either type in the role name to be changed or select it from a dropdown. AGR_TEXTS. So let’s assume that you have none of your own and use one of the SAP role templates provided. Identify the roles(s) to be used as the source for your role copy. On the Role Maintenance screen.AGR_NAME. 5. One the Query popup box. 6. AGR_TCODES.TCODE. TSTCT.AGR_NAME = AGR_TEXTS. Once the role has been copied. Most people will add a Z. The SQL query would be something like this: SELECT AGR_TEXTS. otherwise click the Copy all button.AGR_NAME. Click the Copy role button or press Shift+F11. 4.. Log on to client needing the role.in the first two characters of the role name. 2.TEXT. Back out to the Change Roles screen and click the User tab. .MANDT = '000' AND AGR_TEXTS.TCODE.TCODE ORDER BY AGR_TEXTS. Modifying a User Role 1.. Once the comparision is done.. 3.LINE = 0 AND AGR_TCODES.MANDT = '000' AND AGR_TCODES. Press Enter to confirm that the role is found. This query should be changed based on the details of your SAP instance.SPRSL = 'E' AND TSTCT. Click on User Comparison and then Complete Comparison. Click the Authorizations tab and then the Change Authorization Data button. Change you Role description and save the new role before working with it any further Return to Index.

. Click the green √ to continue. continue to use the same transport you created in step 6. you will need to log on to each of those clients and do a user comparison. 13. On the Role maintenance screen. Deleting a User Role 1. 5. You will also need to do a text comparison in client 100 of the appropriate SAP system. profiles. 7. Your deletion will return a successful message in the bottom status bar. 8. You will see an Information popup. type in the Role name of the first role to be transported. If you get an Information popup. Go to transaction PFCG. Log on to client needing the role deletion. If you want to transport the users along with the role.. profiles. fill in the Short description and click the Save picture-icon. On the Create Request popup.. They can all be added to the same transport change request.. On the Role Maintenance screen. One role. unclick the □s beside User assignment and Personalization.. Click the green √ to continue. the roles must be transported to the 800 client. You will see an Information popup. Go to transaction PFCG. You will see a Data entered in change request message in the status bar at the bottom of the screen. Click the green √ picture-icon. 6. Now enter the name of the next role to be transported and click the Truck picture-icon. 5. You may now leave the PFCG transaction. If you want to transport the users along with the role. 2. either type in the role name to be changed or select it from a dropdown. 6. 1. 10. On the Delete Role popup. confirm that you wish to delete the deletion. In the Choose objects popup. you can √ the □ to the left of User assignment. In the Choose objects popup. several roles. After the roles have been moved to other clients. The generated transport can now be released and transported into the clients needing the modified roles. You will be returned to the Prompt for Customizing request popup which contains the generated change request number for this system change. Click the green √ picture-icon. Click the Truck picture-icon. 4. Click the Role Delete button or Shift+F2. and authorizations. 9. or all roles can be done if needed. 4. 3. Click the green √ picture-icon. 11. On the Prompt for Customizing request popup. Return to Index. On the Prompt for Customizing request popup. Continue to perform steps 7 through 10 until all the roles you need to transport have been attached to the transport change request. click the blank page picture-icon to create a new change request. 3. Click the green √ picture-icon. Transporting User Roles between Clients (Upload/Download Method) . you can √ the □ to the left of User assignment. unclick the □s beside User assignment and Personalization. and authorizations. 2. Transporting User Roles between Clients (Transport System Method) When a modification is made to a role in the 100 client. 12. Log on to client 100 of the appropriate SAP system. Return to Index. Press Enter to confirm that the role is found. confirm it also.

It does not. They can all be added to the same transport change request. The generated transport can now be released and transported into the clients needing the modified roles. Click the Truck picture-icon. 9. Performing a Text Comparison to Refresh Role Selection Lists . 10. You will receive a User master record for role was adjusted message in the status bar at the bottom of the screen. 7. Continue to perform steps 7 through 10 until all the roles you need to transport have been attached to the transport change request. and authorizations. click the User compare button. If you want to transport the users along with the role. click the blank page picture-icon to create a new change request.. you can √ the □ to the left of User assignment. you can √ the □ to the left of User assignment. type in the Role name of the first role to be transported. You will see a Data entered in change request message in the status bar at the bottom of the screen. You will be returned to the Prompt for Customizing request popup which contains the generated change request number for this system change. fill in the Short description and click the Save picture-icon. however. On the Prompt for Customizing request popup. You will see an Information popup. and authorizations. On the Role maintenance screen. 1. Log on to client 100 of the appropriate SAP system. unclick the □s beside User assignment and Personalization. profiles. On the Create Request popup. Click the green √ picture-icon. do the same for roles and role authorizations. 3. 13. 11. In the Choose objects popup. 6. 4. Central User Administration distributes clients and their information to the other clients connected to the Distribution Model. 6. Click the green √ picture-icon. After the roles have been moved to other clients. Click the green √ picture-icon. Now enter the name of the next role to be transported and click the Truck picture-icon.. On the Change Roles screen. You may now leave the PFCG transaction. Return to Index. type in the Role name of the first role to be transported. If you want to transport the users along with the role. On the Role maintenance screen. 7. Click the green √ to continue. unclick the □s beside User assignment and Personalization. Performing a User Comparison on the Modified Roles 1. 5. Return to Index.. One role. or all roles can be done if needed. you will need to log on to each of those clients and do a user comparison.. You may now leave the PFCG transaction. 3. click the Complete compare button. You will also need to do a text comparison in client 100 of the appropriate SAP system. On the Prompt for Customizing request popup. Click the Change button. 8.. several roles. profiles. 12. Click the green √ to continue. You will see an Information popup. Log on to client 100 of the appropriate SAP system. Go to transaction PFCG. On the User tab. In the Choose objects popup. click the User tab. 4. On the Compare Role User Master Record popup. So when a modification is made to a role in the 100 client. continue to use the same transport you created in step 6. the roles must be transported to the 800 client. 2. 5. Go to transaction PFCG. 2. Click the green √ picture-icon.

and Authorizations SAP security is based on authorization objects and authorizations. Log on to client 100 of the appropriate SAP system. and P_GROUP. For example. 5. Go to transaction SU01. Click the pencil picture-icon. Users. This is a range. button. Roles. The authorizations are set to the appropriate values as needed. 4. So S_DEVELOP has a selection of authorizations you can use: ACTVT. An authorization is used to limit the scope of that activity. assistant DEVCLASS Single Value or Value Range OBJNAME Single Value or Value Range OBJTYPE Single Value or Value Range P_GROUP Single Value or Value Range The S_DEVELOP authorization object in a profile lets a user perform ABAP workbench activities. It is important to remember. click the Text comparison from child Syst. This authorization object allows a user to perform ABAP workbench activities. An authorization object is used to indicate that a user can perform a certain activity. that a user with a profile having a S_DEVELOP with full authorizations still cannot . A tree view of the S_DEVELOP authorization object can be seen below: S_DEVELOP ACTVT Create or generate Change Display Delete Activate. a profile contains the S_DEVELOP authorization object. 2. or until you have left the SU01 transaction. Thus we see that authorization objects grant while authorizations limit. all three systems will have the text comparison performed. On the Maintain User screen. On the CUA: Text comparison from Child Systems results screen. type in the user “model_user”. OBJTYPE. and since LSPRD300 falls alphabetically between LSDEV100 and LSQAS800. DEVCLASS. But having a S_DEVELOP authorization object with the ACTVT authorization value set to Display (03) means that the user is limited to display only in the ABAP workbench transactions. Some users will need to do all ABAP activites while others will only need to perform a few. 6... 3. generate Execute Create in DB Delete in DB Convert to DB Administer Copy All Functions Deactivate Mod. however. Click the clock picture-icon. On the User Maintenance: Initial Screen screen. type “LSDEV100” for the Receiving system and “LSQAS800” for the to system.. On the CUA: Text comparison from Child Systems screen. 1. Return to Index. Click the white arrow on green picture-icon 3 times. you will see a list of the systems compared and the compare results. OBJNAME.

11. 3. All authorization objects and authorizations are grouped into profiles before being attached to users. Otherwise. select the authorization you need to add by double-clicking the appropriate line. a user may have the rights to add. activate the dependent . From the Maintain Profiles: Object Classes screen. On the Maintain Profiles: List of Authorizations screen. 10. the easiest method is to copy an existing role that matches your needs as closely as possible and make the changes you need for the new role. If the next screen is titled Maintain Profile. click the Save picture-icon. use the drop down to fill in the Authorization column. 5. On the Maintain Profile screen. If you need to add another authorization to an authorization object already in the profile list. 2. click on the +Add authorization button. Type the authorization object you need to add and press Enter. This documentation covers changing user security via both methods. double-click the Object class of the authorization you are adding. such as the start of a new SAP landscape where no roles exist. 9. with the exception of the Basis team. Go to transaction SU02. or add a new authorization to an authorization object already in the profile. 4. You will need to scroll through the list again until you find the authorization object you just added (it is was to find since the Authorization column should still be blank). But once the landscape has been completed all users. You may now leave the SU02 transaction. he cannot access transaction SE38 which is the ABAP Editor. If you need to add a new authorization to an authorization object already in the profile. 8. There are times. this is a collective profile and you should skip to step 13.. If the next screen is titled Collect Profiles. access an ABAP workbench transaction until a matching S_TCODE (start up transaction code) has been added as well. scroll down the Consisting of authorizations list until you find a blank line. On the Activate Profile: Execution Screen screen. Then click the lit match pictureicon to activate the new profile changes. Roles are created via a more user-friendly interface which generates profiles based on the information added via this interface. In order to simplify the creation of profiles. enter the Profile you want to change. In order the change a profile collection. To add a new role. This will return you to the Maintain Profile screen where you can see that your authorization has been added. you must decide if you need to add a new authorization object and one or more of its authorizations. Log on to the appropriate client in the appropriate SAP system. and their creation can be complex as well as tedious. 12. Once you find the new entry line. skip to step 7. you must make the changes in one or more of the dependent profiles. click on the lit match picture-icon to complete the profile activation process. Adding Authorization Objects and/or Authorizations to a Profile Remember that profiles are NOT the standard way to implement SAP security 1. Manually creating profiles is the “old” way of doing things. On the Profile List screen. 13. In the Manually edit authorization profiles section of the Profile: Initial Screen screen. modify and delete ABAP programs but until an entry for SE38 has been added to the S_TCODE authorization object. and you should proceed to the next step. this is a single profile. There should never be a need to manually create a SAP new profile. Make sure the Active only □ is checked. Click the Create work area for profiles button. In other words. save the changes in the dependent profile(s). Profiles use a combination of authorization objects and their respective authorizations. On the Maintain Profile screen. the Profile Generator (transaction PFCG) was created. 6. 7. A profile can contain authorization objects only (single profile) or one or more other profiles (collective profile). double-click the profile to be changed. Click on the Save picture-icon. should be attached to roles. that the use of profiles is handy.

click the red-and-white beach ball picture-icon to generate a profile from the saved role. If you do not need to add any start up transactions to the profile. click the +Manually button. On the Collect Profiles screen. Click the Change button. On the Change role: Authorizations screen. profile(s). S_PROGRAM. enter the authorizations objects that need to be added (ie S_DEVELOP. double-click on the profile you want to change. click on the lit match picture-icon to complete the profile activation process. On the Change Role: Authorizations screen.. Double-click on the entry portion of the Transaction code line.. 11. You will receive a Data saved confirmation message in the status bar at the bottom of the screen. 2. 14. Return to Index. 14. You will receive a Profile(s) created message in the status bar at the bottom of the screen.. 3. 5. Reply affirmatively if any confirmation popups. you may now leave the PFCG transaction. click the Authorizations tab and then click the pencil pictureicon. On the Manual selection of authorizations popup. 4. 12. You may now leave the SU02 transaction. Log on to client 100 in the DEV SAP system. if all the displayed signal lights are green. click the Save picture-icon.. All signal lights should be green before moving to the next step. Then use the white arrow on green picture-icon to go back. 10. 15. click the Save picture-icon. 16. skip to step 8. Go to transaction PFCG. and activate the collection owner profile. skip to step 10. If you are only adding a start up transaction to the role. and click the Save picture-icon when you have finished. 6. Enter the transaction(s) to be added. click the Save picture-icon. Perform steps 6 to 11. 17. Granting Transaction Access to a User via Profile . Back on the Change role: Authorizations screen. Return to Index. 13. On the Change Role screen. You may now leave the PFCG transaction. On the Collect Profiles screen. Adding Authorization Objects and/or Authorizations to a Role 1. Reply affirmatively if any confirmation popups. 8. On the Change role: Authorizations screen. In the Maintain Field Values popup. expand the Cross-application Authorization Objects → Authorization Check for Transaction Start → Authorization Check for Transaction Start until you see the Transaction code entry line.) Click the green √ when you are finished. On the Change role: Authorizations screen. Then click the lit match pictureicon to activate the new profile changes. scroll down the list until you find a blank From and To line. On the Change role: Authorizations screen. On the Role Maintenance screen. You will receive a Profile(s) created message in the status bar at the bottom of the screen. fully expand the lines that are yellow and/or red and supply the necessary information. Otherwise. On the Activate Profile: Execution Screen screen. the assumption is that a new authorization object is to be added. enter the Role you want to change. On the Change role: Authorizations screen. 9. save the collection owner profile. You will be taken to the Maintain Profile screen. You will receive a Data saved confirmation message in the status bar at the bottom of the screen. 7.. etc. click the red-and-white beach ball picture-icon to generate a profile from the saved role. Otherwise.

. *** Since SAP R/3 4. Make sure to use transaction PFCG to run a user comparion to rebuilt the role-to-user connections.5.5. *** Return to Index. Return to Index. Log on to the applicable SAP instance and client. 4. Click the Save button.. You may now leave the PFCG transaction. this is not the standard for user authorizations.... this is not the standard for user authorizations. *** Return to Index.. Granting Transaction Access to a User via Role 1.. On the Maintain User screen. *** Return to Index. Press ENTER to confirm that the role exists. *** Return to Index.. 2. 5.. either by typing it in or choosing it from the drop down.. this is not the standard for user authorizations. Click the little yellow pencil Change button. . On the User Maintenance: Initial Screen screen. 3. Attaching a Role to a User 1. Revoking Transaction Access from a User via Profile *** Remember that profiles are NOT the standard way to implement SAP security. Revoking Authorizations from a User via Role Use the same procedure as Adding Authorization Objects and/or Authorizations to a Role Return to Index. Attaching a Profile to a User *** Since SAP R/3 4. click on the Roles tab. Go to transaction SU01... Log on to the applicable SAP instance and client. Revoking Authorizations from a User via Profile *** Since SAP R/3 4.5. 6. Fill in the new role in the first available Role field.. fill in the User ID for the user you want to change.

click on the Roles tab. On the Background Print Parameters popup. Click the Save picture-icon.. click the Schedule as background job button. Go to transaction SCCL for Local Client Copy. 5. Press ENTER to confirm that the role exists. *** 1. use the Selected profile dropdown to select a profile that matches your needs. . 5. MM/DD/YYYY. You can monitor this copy by using transaction SCC3. To schedule the copy for a later date and/or time. Client Tasks Client Copies within the Same SAP System *** SAP’s terms for the sending and receiving clients can be confusing. The “target” client is the client into which data is to be copied. Fill in the new role in the first available Role field. you may receive a date validation error if you use the date format of MM-DD-YYYY. if you want the client copy job submitted right away. You will receive a client copy confirmation message. If the target client is new. YYYY. Log on to the target client in the appropriate SAP system. or one of the other SAP provided client copy profiles. There should only be one server available in the dropdown.. If you are unsure as to the format of date and time. On the Client Copy – Copy a Client screen. In the Date/Time section. 6. On the Maintain User screen. Click on the Defaults tab to see your default date format. The only exception is when the SAP_USER profile is used. Return to Index. and YYYY-MM-DD. Try other variations such as DD. On the User Maintenance: Initial Screen screen. On the Verification popup.YYYY. In this case. Type the Source client and Source client user masters in the provided boxes.DD. You may now leave the PFCG transaction. 8. 9. click the Immediate button. click on the top-most menu bar System → User profile → Own data. YYYY/MM/DD. use the Background server dropdown to select the background server on which the job is to run. select an Output device from the dropdown. Click the Save button. 4. You may now leave the SCCL transaction. fill in the User ID for the user you want to change. Click the green √ to continue. Once all information has been provided. provide the Scheduled start Date and Time.MM. 2.. 2... Click the Schedule job button. Also. If you receive a Change documents will not be copied message in the bottom status bar. Create the target client if necessary. 3. These two boxes should contain the same client number unless the data is to come from one client and the user master data from a different client. SAP_USER to copy only user master data. On the Schedule Client Copy in Background screen. click the Date/Time button. 7.MM. If the user is SAP* due to a new client. use “SAP*” for the user and “pass” for the password. Return to Index. only user master data is deleted from the target client before the new user master data is copied. Go to transaction SU01. The “source” client is the client which contains the data to be copied. Click the little yellow pencil Change button. check that everything is correct and click the Continue button. Make sure to use transaction PFCG to run a user comparion to rebuilt the role-to-user connections. click the green √ next to the transaction command field at the very top of the screen to continue. either by typing it in or choosing it from the drop down. 4. Use SAP_ALL or SAP_UAPP to copy all data except change documents. On the Start Time popup. remember that all client copies are destructive and will delete all data before copying in the new data. 3. 6.

and YYYY-MM-DD. you will need to create one..MM. The only exception is when the SAP_USER profile is used. MM/DD/YYYY. . If the target client is new. use the dropdown to select the remote source client. You will receive a client copy confirmation message. click the Immediate button. provide the Scheduled start Date and Time. Since role changes don’t transport across the other clients maintained via Central User Administration. Client Copy Variations Limiting a Client Copy to Refresh User Master Data Sometimes you need to retain the data residing in a client but refresh the roles. On the Verification popup. On the Client Copy – Copy a Client screen. Click the Save picture-icon. Click the green √ to continue. 4.YYYY. 6. On the Schedule Client Copy in Background screen. you may receive a date validation error if you use the date format of MM-DD-YYYY. If you receive a Change documents will not be copied message in the bottom status bar. Also. 8. If you are unsure as to the format of date and time. Log on to the appropriate client on the appropriate SAP system. To test that your select Source destination RFC connection will work.. and other security components that have changed in DEV client 100. remember that all client copies are destructive and will delete all data before copying in the new data. If the user is SAP* due to a new client.MM. click the green √ next to the transaction command field at the very top of the screen to continue. On the Background Print Parameters popup. if you want the client copy job submitted right away. To schedule the copy for a later date and/or time. There should only be one server available in the dropdown. click the Schedule as background job button. YYYY/MM/DD. Once the proper remote source client has been selected. a Source destination must be provided. YYYY. the System name and Source client boxes will fill automatically. In the Date/Time section. 1. This is a RFC connection pointing to a specific client in another SAP system. Go to transaction SCC9 for Remote Client Copy. 9. SAP_USER to copy only user master data. click on the top-most menu bar System → User profile → Own data. click the RFC system check button. Use SAP_ALL or SAP_UAPP to copy all data except change documents. Otherwise. *** 1. Click on the Defaults tab to see your default date format. In this case. Create the target client if necessary. use the Selected profile dropdown to select a profile that matches your needs. Log on to the target client in the appropriate SAP system. Since this is a client copy that uses data from a client in another SAP system (or remote client). Return to Index. a user master client copy can be used on any client in the SAP landscape. check that everything is correct and click the Continue button. If there is no RFC connection to the client you wish to copy. only user master data is deleted from the target client before the new user master data is copied.DD. use “SAP*” for the user and “pass” for the password. select an Output device from the dropdown. users. The “target” client is the client into which data is to be copied.. 7. Try other variations such as DD. Once all information has been provided. click the Date/Time button. use the Background server dropdown to select the background server on which the job is to run. 2. Click the Schedule job button. On the Start Time popup. The “source” client is the client which contains the data to be copied. 3. You may now leave the SCC9 transaction. 5. You can monitor this copy by using transaction SCC3. Client Copies between Different SAP Systems *** SAP’s terms for the sending and receiving clients can be confusing. or one of the other SAP provided client copy profiles.

check that everything is correct and click the Continue button. If you are unsure as to the format of date and time. Log on to any client in the “target” SAP system. On the Background Print Parameters popup.. 4. use the Selected profile dropdown to select profile “SAP_USER”. 4. if you want the client copy job submitted right away. This should be the client that contains the user master data you want to copy. From the list of Client copy logs. Double click on any of these summary lines to see statistics for a particular copy client job. If the user master data is coming from a client within the same SAP system. On the Schedule Client Copy in Background screen. On the Verification popup. 6. click the pencil and glasses picture-icon to switch into change mode. *** 1. Once all information has been provided. provide the Scheduled start Date and Time. a Source destination must be provided. 7. use the Background server dropdown to select the background server on which the job is to run. 8. whichever is appropriate. click the Immediate button. go to transaction SCCL. click on the top-most menu bar System → User profile → Own data. Go to transaction SCC4. You can monitor this copy by using transaction SCC3.) If so.. You may now leave the SCCL or SCC9 transaction. 2. Return to Index. Type in the same client for both the Source client and Source client user masters. select an Output device from the dropdown. Return to Index. Log on to any customizable client in the appropriate SAP system.. There should only be one server available in the dropdown. 5. In the Date/Time section. You will receive a client copy confirmation message. 2. Viewing the Client Copy Logs 1. To schedule the copy for a later date and/or time. 2. 3. . If you receive a Change documents will not be copied message in the bottom status bar.. 5. On the Client Copy/Transport Log Analysis screen. click the All clients button. On the Display View “Clients”: Overview screen. 3. You may now leave the SCC3 transaction. If the user master data is to be copied from a client in another SAP system. If this is a user master copy that uses data from a client in another SAP system (or remote client). On the Client Copy – Copy a Client screen. etc. Click the green √ to continue. source for client copies. click the Schedule as background job button. go to transaction SCC9. Click the Save picture-icon. On the Start Time popup. the new client will need to be assigned a Logical System ID that is unique among all the SAP systems in the landscape. double click on a client to view summary information for all client copies where this client was the target client. It is recommended that all new clients be assigned to a Logical System ID as soon as they are created. Click the Schedule job button.. Click on the Defaults tab to see your default date format. Go to transaction SCC3. 3. click the Date/Time button. Creating and Deleting Clients Creating a Client *** Before adding a new client you should first ask if it will be used in communications with other clients (Central User Administration. click the green √ next to the transaction command field at the very top of the screen to continue.

. click the New Entries button. Log on to the client to be deleted. 7. Deleting a Client 1. the information listed in the SCC4 can be confusing. 3. On the Start Time popup. In the Date/Time section. click the green √ to dismiss the informational message. On the Schedule Client Copy in Background screen. click on the top-most menu bar System → User profile → Own data. On the New Entries: Details of Added Entries screen. Client-independent object changes.. You may now leave the SCC4 transaction. Restriction Change Levels in a Client When adding a new client to a SAP system. select an Output device from the dropdown. If you also want the client deleted for T000 (ie the scc4 entry). You will receive a client copy confirmation message. Possible roles are: * * * * Production client Test client Training client Demo client . Click the green √ to continue. click the Save picture-icon. This is a brief explain of the available client restrictions. There should only be one server available in the dropdown. You may now leave the SCC5 transaction. verify that you are deleting the correct client. click the Immediate button. If you are unsure as to the format of date and time. Protection: Client copier and comparison tool. On the Verification popup. select the necessary restriction levels from the provided dropdowns. 6. On the Change View “Clients”: Overview screen. On the Display View “Clients”: Overview popup. Use the Logical system dropdown to assign a logical system ID to the client. Click on the Defaults tab to see your default date format. 4. On the Background Print Parameters popup. provide the Scheduled start Date and Time. use the Background server dropdown to select the background server on which the job is to run. click the Date/Time button. Return to Index. Click the Background button.. Don’t panic. In the Changes and transports for client-specific objects. 6. 5. 2. Type “USD” in the Std currency box. Client role: The category indicates the role of the client in your R/3 system. if you want the client delete job submitted right away. Once all information has been provided. On the Delete Client screen. it looks like a client copy confirmation and says nothing about this being a delete job. put a √ in the □ to the left of Delete entry from T000 by clicking the □. Click the Schedule job button. check that everything is correct and click the Continue button. 5. Select a Client role from the client role dropdown (remember that there can only be one Productive client per SAP system). Click the Save picture-icon. You will see a Data saved in the status bar at the bottom of the screen. 4. and Restrictions when starting CATT and eCATT sections. fill in Client number and description and the City. Go to transaction SCC5. 8. You can monitor this copy by using transaction SCC3. To schedule the delete for a later date and/or time. 7.

to enable adequate protection of a productive client in a system with further (test) clients. SAP is planning to link further effective functionality to this flag. . exchange rates. this means current settings (e.0 also ensures the following: If there is a productive client in the target system. This is the usual configuration for a production client where customization should not be performed. Automatic recoding of changes – the client can be customized and all changes are generated into change requests. inconsistencies may occur in all clients. No changes allowed – no modifications can be made to the client – it is protected or locked. use the SCC4 transaction to assign the logical system to a client. Other settings for a client: Change and transports for Client Dependent Objects Changes without automatic recording – the client can be customized although the system will not generate change requests. Adding a logical system to a client after the client has been in existence and in use to a long time period could cause referencing problems between that client and the rest of the SAP systems. Client-Independent Object Changes Changes to repository and client-independent customizing allowed – no restrictions on this client for changes and development. no client copy (remote copy) which also selects cross-client customizing objects may be imported into the system. If crossclient settings are imported. Normally. Creating a Logical System ID to be Assigned to a Client A logical system gives a client a unique “name” which can be referenced by other clients within the SAP landscape.. you create the logical system before creating a client so that both start out together. No transports allowed – changes are allowed but cannot be transported.. Release 3. Return to Index.g. No changes to repository and client-independent customizing objects – this setting prohibits any client-independent modifications and is common on Production systems. customizing settings that can be maintained as "current settings" can be excluded from a client lock or transport links. No changes to client-independent customizing objects . No changes to repository objects – lets users perform client-independent customizing but no development or modifications to repository objects. * * Customizing client SAP reference client This field should be maintained by the customer for Documentary purposes. Once you have created a logical system. posting periods) can always be maintained in a productive client without recording changes.allows for development on repository objects but not client-independent customizing. In a productive client..

On the Display IMG screen. and Password for an existing user in the target RFC SAP system.. click the Create button. On the RFC Destination screen. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Log on to any customizable client in the appropriate SAP system. 4. On the Create Request popup.. On the Display and maintain RFC destinations screen. Communications Tasks Creating.. If the target is another SAP system. On the Change View “Logical Systems”: Overview screen. Click the Save picture-icon. You will receive a Destination saved message in the status bar at the bottom of the screen. 2. Fill in the Language. expand the navigation tree like so: Application Link Enabling (ALE) Sending and Receving Systems Logical Systems Define Logical System 4. enter the number of System number (00 for all SAP systems except BW QAS which needs a 01). Log on to any client on the appropriate SAP system. and Deleting RFC Connections Creating a RFC Connection 1. 8.. click the Save picture-icon. 3. User. .. This user should be a system or communication user (ie RFC_USER or ALEREMOTE). click the New Entries button. fill in the necessary client logon information in the Logon section. click the clock picture-icon to the left of Define Logical System. You may now leave the SM59 transaction. Click the green √ to continue. 7. 2. Select the Connection type from the connection type dropdown. Return to Index. 5. Modifying. Press Enter. fill in the Short description and click the Save picture-icon. 5. 6. On the Prompt for Workbench request popup. In the Technical settings section of the RFC Destination screen. On the New Entries: Overview of Added Entries screen. You will receive a Data saved message in the status bar at the bottom of the screen. 9. Once all this information is provided. Return to Index. type in a RFC destination name. Client. such as “LSDEV100” for DEV Client 100. not a dialog user. Go to transaction SM59. press Enter. On the Display IMG popup. If the connection type is a “3” (another SAP system). This name should contain meaningful information such as the SID of the SAP system and/or any client numbers. System and Name. and type the connection specifics in the Description box. 6. On the RFC Destination screen. click the green √ button to dismiss the informational message. You may now leave the SALE transaction. 3. fill in the Log. On the Display IMG screen. The description should be uniform as well such as “Logical System for DEV Client 100”. 1. The logical system should match the naming convention already in place: LS<SID><Client Number>. Go to transaction SALE. type in the name or IP address of the Target host. click the blank page picture-icon to create a new change request.

.
Modifying a RFC Connection 1. Log on to any client on the appropriate SAP system. Go to transaction SM59. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and double click the RFC destination to be changed. On the RFC Destination screen, make any necessary changes. Once the information is changed, click the Save picture-icon. You will receive a Destination saved message in the status bar at the bottom of the screen. You may now leave the SM59 transaction.

2. 3. 4. 5.

Return to Index... Deleting a RFC Connection 1.

2. 3. 4. 5.

Log on to any client on the appropriate SAP system. Go to transaction SM59. On the Display and maintain RFC destinations screen, expand the appropriate RFC destination navigation level and click the RFC destination to be deleted. Click the Delete button. On the Delete destination popup, click the Yes button. You will not receive a confirmation message. You may now leave the SM59 transaction.

Return to Index... Testing a RFC Connection Return to Index... Database Tasks Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – MS SQL Server Database statistics refresh jobs should be scheduled to run twice daily on all the SAP systems. But occasionally a manual refresh needs to be done due to table reorganization, index rebuild, etc. 1. 2. 3. 4. Log on to the server using the <sid>adm user ID. Open the MS SQL Server Enterprise Manager. Expand the navigator tree until you see the Management entry. Expand it. Right-click on Database Maintenance Plans and click New Maintenance Plan. Use the wizard to create the job you need. You may now close the Enterprise Manager session and log off the server.

5.
6.

Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – Oracle 1.

2. 3. 4.

Log on to the appropriate SAP instance any client. Go to transaction DB13. On the DBA Planning Calender for Oracle Database <SID>: Maintain screen, double-click on a blank line on any day in the future. On the Schedule Action for <Day>. DD.MM.YYYY popup, use the radio button to turn “on” the task you want to do. For each action, you need to fill in the Start Time in military time format, the Period (Weeks) which is how many weeks between running of this job – blank

.
for one time only, 1 for weekly, 2 for bi-weekly, etc. and Calender if you want to use any calendar except the SAP supplied standard Factory calendar. These are the details for each action: Whole Whole Whole Whole database offline + redo log or database offline backup or database online + redo log or database online backup Generic tape names for database backup Database backup profile – usually init<SID>.sap Options for ReDo log backup Redo log backup Generic tape names for database backup Options for ReDo log backup Partial database offline backup or Partial database online backup Tablespace names to be included in the back up Generic tape names for database backup Database backup profile – usually init<SID>.sap Check and update optimizer status Tablespace names to be included in the statistics run Adapt next extents Tablespace names for next extents adaption Check database N/A Verify database Tablespace names to be verified Database backup profile – usually init<SID>.sap Cleanup logs N/A

5.

You may now leave the DB13 transaction.

Return to Index... Jobs, Job Logs, and the Job Queue Scheduling a New Job 1. Log on to the appropriate SAP instance and client using BATCH_USER. 2. Go to transaction SM36. 3. On the Define Background Job screen, fill in the Job name field with the new job name. Select a Job Class priority of A for High, B for Medium, and C for Low. It is SAP’s recommendation that all client-owned jobs begin with a Z for identification purposes. And most Basis people recommend the next two characters be the initials for the SAP module for which the SAP instance runs. Like ZBC* for a Basis job, and ZHR* for a Human Resources job. Click on the Specify start condition button or press F5. 4. On the Start Time popup, click the Immediate button to start the job right away, or click the Date/Time button to specify a date/time in the future for which the job run. Click “on” the Periodic job radio button and then click the Period values button if you want to schedule to job to run on a periodic basis. Provide the periodic values and click Save back to the main Define Background Job screen. 5. On the main Define Background Job screen, click the Step button. 6. On the Create Step 1 popup, fill in the ABAP program Name and any Variant needed to run the program – you had to have created the variant using BATCH_USER before using it here. Then click Save once more.

.
7. Back on the Define Background Job screen, check that all the job information is correct and then click the Save button one last time. Return to Index... Modifying a Released or Scheduled Job 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be changed. In order for a job to be changed, it has to have a status of Schedule or Released so turn those statuses “on” and turn the rest “off”. Click on the Execute button. 4. On the Job Overview screen, click “on” the line containing the job to be changed and then click Job → Change. 5. On the Change Job screen, make your changes and then click Save. If you have more than one occurance of the same job in your list, you must change each job scheduled to run earlier than that job you just changed. Once the job you changed runs, all occurences of the jobs running after that date will be changed as well. Return to Index... Deleting a Released of Scheduled Job 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job to be deleted. In order for all occurances of a job to be deleted, all statuses of the job should be checked “on”. And enter an all-encompassing date like 01-01-1990 through 12-31-2010. Click on the Execute button. 4. On the Job Overview screen, click “on” all the perpetent line containing the job(s) to be deleted and then click on the Delete job from database button. 5. On the Delete Scheduled Jobs? popup, confirm the deletion. Return to Index... Viewing the Job Queue 1. Log on to the appropriate SAP instance and client as either the user ID owning the job or an administrator ID. 2. Go to transaction SM37. 3. On the Simple Job Selection screen, fill in the Job name field or use any of the screens filtering options to produce a list from which you can see the job you want to view. In order for all occurances of a job to be viewed, all statuses of the job should be checked “on”. Click on the Execute button. Return to Index... Deleting an Active aka Runaway Job Opinions on this topic vary so these are good guidelines to use. These are pretty much in the order they should be tried:

If the Work Process in SM50 is in stopped state then killing it will not help much or quickly. and kernel patches for application Applying the new SPAM updates. Checking for New SPAM Updates. Try End session through SM50 or cancel program from SM66. Kill process or PID via program RSBDCOS0. It is suggested that Delete with forced mode be “on”. a final total of jobs logs cleaned will appear in the bottom Status Bar.) Try and end those.. the poor old thing is just trying to recover rollback and reinitialize itself.. on the other hand. Support Packages and Kernel Patches. fill in the filtering information you need. Support Package and Binary Patch Tasks In order to apply new support packages and kernel patches to a SAP system. Go to transaction SE38 and type in Program name RSBTCDEL and click on the Execute button. 5. If all else fails. several preparation steps are required: • • • • • Checking for new SPAM updates. Please refer to the Check for New SPAM Updates. Return to Index. Allow it a long time to stop. you need to identify why it is stopped (running a program on another server. support packages and kernel patches Downloading the new SPAM updates. 3. Support Packages and Kernel Patches .. Return to Index. A status message will appear in the bottom Status Bar as the list of job logs to be deleted is built. 2. 4. Once all the specified job logs have been deleted.. 1. 2. 3.. On the Delete batch jobs screen. and kernel patches Mass recompiling all programs used in patched components Be aware that SPAM/SAINT update and support package application occurs within the SAP system using the SPAM transaction. and kernel patches Preparing the new SPAM updates. Kernel patches must be applied when the SAP instance is down. there is no need to do it twice or 50 times as I have seen some people do. runing in parallel etc. restart the SAP instance server.. Change to restart = no as otherwise the session can jump back in sometimes as most of its memory is not actually living in the WP. Log on to the appropriate SAP instance and client. 6. Kill Work Process in SM50 without core. Kill the session via SM37 or SM04. support packages. Return to Index. 4. The most important things to remember when killing a WP are: 1. support packages. Cleaning the Job Log 1. support packages.. Click on the Execute button. 2. are fixes to SAP executables found on the SAP server. These corrections are changes to ABAP program code and must be handled in a special way by SAP. Kernel patches.

you will see the support package level for each component installed in your current SAP instance. On the Support Package Manager screen. click System -> Status… On the System: Status popup. any client. Log on to your SAP instance. 3. Method Two: 1. you need to know your current support package and kernel release levels. Log on your SAP instance. 4. click on the server for which you need the information and then click on the Release Notes button. On the OCS Package Directory: Imported Packages screen. To check if SAP has released any new software fixes for your release of SAP. On the System: Component Information popup. On the SAP Servers screen. 3. At the Linux prompt. The patching process consists of: finding you current patch levels finding what patches you should be applying downloading the patches unCARing the patches loading the patches into the patching EPS queue applying the patches Return to Index. 2. On any SAP screen. 4. type: disp+work –v and press ENTER. Go to transaction SM51. Find your Current Kernel Patch Level Method One: 1.. On the SAP Release Information from Server screen. 4. you will see a list of all SAP Support Packages imported into your current SAP instance. you will find the current patch level of your current SAP instance. Method Two: 1. Find your Current SPAM Update and Support Package Level Method One: 1. Log on to the SAP instance sever using a Telnet session as user <sid>adm. Return to Index.. click the Component Information button. Go to transaction SPAM.. 3. look down the SAP R/3 Kernel information section until you find Kernel Patch number. turn “on” the radion button beside the Imported Support Packages in the Directory section of the screen. 2. 2. To the right. any client. Log on to your SAP instance. . 3. and then click Display button. any client.. 2. Change the Telnet windows properties to use a Screen Buffer Size of 9999..

For example. 4. Scroll back up the listing to where you entered the command in step c.20 3.20 instance but runs on a 6. 1. to find new patches for SPAM/SAINT for CRM 6. Find the Most Current SAP SPAM Update 1.. If this SPAM version is higher than you current SPAM version. Click the Download tab of the SPAM/SAINT UPDATE screen. You may now leave the SAP Marketplace. 2. Return to Index.com/patches. Find the Most Current SAP Kernel Patches 1.sap.0 has a Basis level of a 6. You may leave the SAP Marketplace. For example. Return to Index.. Return to Index. Find the SPAM/SAINT Update – Version XXX value. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service.. Scroll down the Download screen until you find your current package level.20 SPAM/SAINT UPDATE 6. For example.20 expand as follows: Support Packages and Patches My Company’s Application Components SAP SPAM/SAINT UPDATE SPAM/SAINT UPDATE 6. In the navigator tree on the right-hand side of the My Application Components screen. Find the Most Current SAP Support Packages It should be noted here that sometimes an older SAP may run on a newer SAP Basis level. . 2. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. Scroll down the listing untill you find a line beginning patch number. 5. In the navigator tree on the right-hand side of the My Application Components screen. 4..sap.. 4.. So make sure that the kernel patches you download match the SAP R/3 Kernel located via SM51. Any support packages after your current level will need to be applied to your SAP System.0 Entry by Component CRM Server SAP BASIS 6.com/patches.40 kernel. CRM 4. you will need to download and apply the latest SPAM update.20 3.sap. to find new patches for CRM Basis expand as follows: Support Packages and Patches My Company’s Application Components SAP CRM SAP CRM 4. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service..com/patches. To the right is the patch number for the SAP instance hosted on this server.

Return to Index.. To download a SPAM/SAINT update. click the Save button.0 expand as follows: Support Packages and Patches My Company’s Application Components SAP KERNEL 32-BIT SAP KERNEL 6. In the navigator tree on the right-hand side of the My Application Components screen. Scroll down the page until you find the SAPEXE*.SAR is the one you need to download. you may leave the SAP Marketplace.20 expand as follows: Support Packages and Patches My Company’s Application Components SAP SPAM/SAINT UPDATE SPAM/SAINT UPDATE 6. 2. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service.20 3. In the navigator tree on the right-hand side of the My Application Components screen. For example. 2. select a location to store the SPAM/SAINT update and click the Save button.40 32-BIT Linux on IA32 32bit ORACLE & #Database independent 3. You may leave the SAP Marketplace. to find new patches for SPAM/SAINT for CRM 6. click on the SPAM/SAINT Update Title hyperlink. For example. Download SAP Support Packages 1.0 . Click the Download button. Alternatively. to find new patches for CRM 4.. On the Save As popup.20 SPAM/SAINT UPDATE 6.. 2.SAR that matches the same number as the SAPEXEDB*. For example. 4. Unless SAP has instructer you to use a different kernel. you may add the patch to your SAP Download Manager and download all patches in one batch group. In the navigator tree on the right-hand side of the My Application Components screen. to find new patches for CRM Basis expand as follows: Support Packages and Patches My Company’s Application Components SAP CRM SAP CRM 4. You may leave the SAP Marketplace.SAR files.com/patches. On the File Download popup.. the most recent SAPEXEDB*. Scroll down the Download screen until under the File Name column you find SAPEXEDB*. 4.com/patches.SAR you found in the previous step. 5. These two files will give you a complete kernel replace. Now go to the @Database independent section in the same list as ORACLE was displayed. Return to Index. Download SPAM/SAINT Updates 1..sap. Once you have downloaded your SPAM/SAINT updates. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service.sap.

Once you have downloaded the kernel patch. On the File Download popup. you may leave the SAP Marketplace.com/patches.0 expand as follows: Support Packages and Patches My Company’s Application Components SAP KERNEL 32-BIT SAP KERNEL 6. For example. Return to Index.SAR. Alternatively.. To download a support package. The full path would look like this: Support Packages and Patches My Company’s Application Components SAP KERNEL 32-BIT SAP KERNEL 6. and kernel patches. Download SAP Kernel Patches 1. On the File Download popup.20 3. Make sure that the version number of your database independent files matches the version number of your MS SQL Server dependent file. This produces a list of database independent kernel patches.. Now backup a step and instead of clicking ORACLE. Download Other SAP Binary Patches Unlike SPAM/SAINT updates. Click the Download button. Return to Index. the storage location for other SAP binary patches can be either SAP Marketplace or sapserv1. to find new kernel patches for CRM 4. you may leave the SAP Marketplace. click on the SAPEXEDB_<version>. Once you have downloaded as many support packages as you need to apply.40 32-BIT Linux on IA32 32bit #Database independent 5. you may add the patch to your SAP Download Manager and download all patches in one batch group. support packages.40 32-BIT Linux on IA32 32bit ORACLE 3. On the Save As popup. click on the package Title hyperlink. ... SAP Marketplace is the normal respository but if you can’t find your patch there. On the Save As popup. Click the Download button.SAR hyperlink. select a location to store the support package and click the Save button. you may add the patch to your SAP Download Manager and download all patches in one batch group. go look on sapserv1. 6. To download a kernel patch. 4. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service.sap. Scroll down the Download screen until under the File Name column you find SAPEXE_<version>. click #Database independent. Use the same instructions in step 5 to download the patch. click the Save button. In the navigator tree on the right-hand side of the My Application Components screen. select a location to store the kernel patch and click the Save button.. Entry by Component CRM Server SAP BASIS 6. 4. Alternatively. 2. click the Save button.

5. Return to Index.EXE. The SAP instance must be down before a kernel patch can be applied. You may now leave the server. 7. 1. Logon the server to be patched as <sid>adm. Go to transaction SPAM. You can place the SAPEXE*. The progress of the support package loads will show in the status bar at the bottom of the screen.SAR and SAPEXEDB.SAR files must be uncompressed using SAPCAR.SAR files in any directory and use the SAPCAR. 8.?AR file to the /usr/sap/trans/tmp directory on the SAP Transport Domain Server which is normally the DEV server of a SAP “Flavor”. Prepare a Kernel Patch for Application Kernel patches must be applied on the SAP server. Everything should now to accessible via SAP Marketplace. Application of SPAM/SAINT Updates . Prepare a SPAM/SAINT Update or Support Package for Application Once you have downloaded your SPAM/SAINT Update and/or support package(s).. they must be moved to the appropriate transport directory and uncompressed.. Use the Go Back icon to return to the previous screen. click Support Package → Load Packages → From application server. move the downloaded K*. Log on to the appropriate server as <sid>adm. 10.?AR” to unCAR the files.*** Return to Index. Prepare other SAP Binary Patches for Application Use the same procedure as Preparing a Kernel Patch for Application. Log on client 000 of the appropriate SAP system. Type the following: cd /usr/sap/trans ¬ SAPCAR.. Log off the server..EXE -xvf “tmp\*. On the SPAM: Confirm upload popup.. The downloaded SAPEXE*. For a SAP instance.?AR” ¬ This will unCAR all CAR and SAR files in the \usr\sap\trans\tmp directory to the /usr/sap/trans/EPS/in. ***Due to the shutdown of the sapserv1x servers in April. 9.. 3.. 6.. Return to Index.EXE –xvf “*. You may now leave the SPAM transaction. 2. From the menu bar of the Support Package Manager screen. 2. 4.. this section has been discontinued. click the green √ picture-icon. 3. Scroll down the SPAM: Uploading Packages from the file system screen to make sure your SPAM/SAINT update is listed. 1. Return to Index.

Once you are again on the Support Package Manager screen.6. 3. When the Restart SPAM popup appears. These messages look very similar to the messages generated during a change request transport. The component order support packages should be applied is SAP_BASIS. See SAP Note 782140 for information on restrictions to grouping support packages into queues. 1. This is normal. 8. Log on client 000 of the appropriate SAP system. Return to Index. please pull the OSS Note 782140 . A list of all application support packages for the selected component will appear in the Define Queue popup. Click the green √ picture-icon to continue. 2.OCS: Known problems with Support Packages in Basis Rel.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch. On the Component Selection popup. The Package ID with the green √ to the left is the highest support package to be placed in the queue. Repairs are usually advanced corrections obtained from SAP Notes that are eventually accumulated into support packages.. SAP_APPL. You may now leave the SPAM transaction. You may notice programs compiling in the status bar at the bottom of the screen. Go to the SPAM transaction. 4. Go to the SPAM transaction. 4. Once you have loaded the latest SPAM/SAINT update into your support Package manager buffer. Once you have loaded the latest support packages into your support Package manager buffer. 7. Application of SAP Support Packages Before applying any support packages to your SAP system.. From the menu bar of the Support Package Manager screen. verify that the SPAM status in the Status section of the screen contains a green light. Go to the SPAM transaction. On the Support Package Manager screen. 2.. release all “repair” change requests to prevent error messages due to locked resources. So the same objects “repaired” in the advanced corrections will be “repaired” during the application of the support package. The progress of the SPAM/SAINT update application will be displayed in the status bar at the bottom of the screen. Before you apply the most current SPAM/SAINT. 5.Known problems with transaction SAINT in Basis Release 6. Before you apply the most current SPAM/SAINT. Releasing the repair change requests allows the support package to overlay the temporary advanced correction “fix”. click the Display/Define button to build your import queue. 3.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch. and PI. you need to apply the update to your SAP system. . click Support Package → Import SPAM/SAINT update. click on the Comp. click the green √ picture-icon to leave the SPAM transaction. you need to apply the packages to your SAP system. 6. SAP_ABA. ID having support packages you want to install. Log on client 000 of the appropriate SAP system using a adminitrator user ID that is not DDIC or SAP*. Click the green √ picture-icon to confirm the queue. please pull the OSS Note 484219 . Select the support packages you want to apply. 1. All lower number support packages for this component will be applied as well.

. click the green √ picture-icon. After the successful completion of the kernel patch. 4. click the green √ picture-icon to continue. copy the new files into usr\sap\<SID>\SYS\exe\run directory. What has changed since the performance is poor?  System Parameter Changes (RZ10)? . read the displayed information and then click the green √ picture-icon to continue. say yes to all. 9. Log on to the appropriate server as <sid>adm. If prompted for overwrites. To confirm that your support packages applied completely. You are ready to build another support package queue. From the menu bar of the Support Package Manager screen. 5. and SAP<SID>_00 services are stopped. 8. you may now leave the SPAM transaction... Application of SAP Kernel Patches *** It is recommended that the /usr/sap/<SID>/SYS/exe/run directory be copied to /usr/sap/<SID>/SYS/exe/backup_run before replacing the kernel *** 1. Application of other SAP Binary Patches Use the same procedure as Application of SAP Kernel Patches. 10.. A Support Package queue was confirmed message will appear in the status bar at the bottom of the screen. After the new kernel has been copied make sure that the following file ownerships are correct: All files in /usr/sap/<SID>/SYS/exe/run /usr/sap/<SID>/SYS/exe/run/saposcol /usr/sap/<SID>/SYS/exe/run/br* /usr/sap/<SID>/SYS/exe/run/sapdba <sid>adm root ora<sid> ora<sid> 5.. On the SPAM: Import Queue popup. On the Support Package Manager screen. you may bring the instance back up and log off the server. Other SAP Issues SAP System Response Troubleshooting 1. verify that the SPAM status in the Status section of the screen contains a yellow light and the Next action value is Confirm queue. Return to Index.. or if you have applied all the necessary support packages. To apply the new kernel patch to a R/3 instance. The progress of the support package application will be displayed in the status bar at the bottom of the screen. Return to Index. 7. 6. Double check that the SAP instance.. click Support Package → Import queue. When the Imported successfully Information popup displays. Return to Index. 2. SAPOSCOL. 3. These messages look very similar to the messages generated during a change request transport.

5. If only few transactions are affected by the performance problem.     SM50: → Process → Trace → Components – is there a Trace level set? Is it greater than 1? What is the utilization of the work processes? Click the white clock picture-icon. 3. The sorted results shows the top tables when it comes to rows changes per month. These tables are your “database hogs”.< 1% of average response time . you should additionally note the following points: 1. What is the utilization of the disks? How high is the paging in the base pool? 4. Check whether modifications were made in the affected or related transactions. the corresponding parameter should be increased.approx 40% of average response time Wait time -. ST03: → Select a server → Today's Workload: What are the response times? In the case of poor response times. 6. Look for tables that have experienced unusual monthly growth. 4. DB02 → Space Statistics button Press Enter on the Tables and Indexes popup History → All objects off/on Click the Months button Click on the first number under the Rows – Chg/Month header and click the Sort button. ST03: Display the corresponding performance records. 4.1 second (dialog). 2. 3. 5. Is the total CPU for the last dialog process > 10 minutes? ST04: Is the database monitor activated? If yes. To which extent are the hardware resources utilized? Call ST06 at times with poor system performance. 6. ST02: Check the buffering quality. If paging occurs in a buffer. you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way. 1. < 1 second (update) CPU time -. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. ST05: If the database times are high.. What is considered “normal” response time? Performance Standards: Response time -.SM21? Places to look:    2. 3. 2.   Increase in the number of users? Kernel patch? Support Packages? Linux and Oracle patches? Hardware Changes? Any signs of general problems in the System Log . where is most of the time needed? Button 'Top Time': Are there a lot of different transactions with poor response times or are there only a few? Is a certain transaction always slow or only sometimes? ST06: → Detail analysis menu → Hardware Info. Also refer to SAP Note 121625 in this context. it should deactivated it in normal operation. SE30: Carry out a runtime analysis for the affected transactions.

and attach the zipped file to it.< 25 ms High Value Indications: DB request time –. If your installaion was never able to complete due to the instance not being able to start up. and the installation completed 100% successfully.< 10% of average response time DB request time -.log”. • • • • • • • • • have you changed any instance paramters? did you do a kernel replacement for some reason? have there been SAP Support Packages applied that might necessitate a kernel replacement? have there been OS patches? is the database archiver stuck or hosed? has a crucial directory run out of space? has a semaphore or ipc segment gotten stuck from a previous run? is your memory so fragmented that it can’t get enough primary space to start the instance? has someone changes the directory privileges? To investigate an unsuccessful start up. then something has probably changed that makes it not come up. go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. look at the logs in the /home/<sid>adm directory. . zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory. dev_disp. Use the sapinst directory to search the installation logs and find your problem. Also provide them with the answers to the above questions as well as your current hardware and database platforms. Load time -. If all else fails.Buffer problems Wait time -. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. dev_ms. The most useful information can be found in the dev_wx. patch level for SAP support packages. look for “error” in all files with the suffix “.. and stderrx files.Database or index problems Load time -.< 40 ms Changes -. If nothing obvious is found. If you have a test searching tool..< 10 ms Sequential reads-. dev_rfcx. and anything else you might think useful.approx 40% of average response time Database Standards: Direct reads -. you know that the instance itself must be viable. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. or an old one. kernel. SAP System Start Up Troubleshooting Whether you are trying to start a brand new SAP instance. the issue is probably due to lack of resources.Not enough work processes Locked tasks Long running transactions Return to Index.. If your SAP instance has been up and running fine for a good while. and the OS. If this is a brand new SAP instance. open a problem with SAP. there are some very specific places to look for information.

you are applying support packages and get an import error with the following message "Panic! Panic! Panic! there's no object header". Moral of the story? Realize that some things just don't translate correctly from language to language. If you didn't find a note that matched the problem.. And if that produced nothing tangible. But sometimes things get lost in translation. current and precise information.05.. known problems with applying patches. For example. Why? Because it might contain information leading to other notes that did pertain. you could make your next search a little less specifc..42 BR602W No valid SAP license found . you should read the SAP Note even if it didn't look as if it pertained 100%.. or b) deleting and installing a newer version of SAPGui. we have to guess that the English word "Panic!" somehow was translated from the German word "Warning!" and that we can temporarily delay a panick attack until we can research the error. and if you had no luck. like "brbackup No valid SAP license found". and not least.. If you get at least one hit. Return to Index."? And how often have you gone to SAP Marketplace and done a search yourself and found a hit? If we only had a had a nickle. you could search for all words.anf 2004-02-27 00. SAPGui Troubleshooting If a user seems to be experiencing SAPGui errors. you could try "warning message no object header". These are mostly lists of supported printer devices.. read and become familiar with your SAP Notes. There are certain notes that you pull over and over again due to some task that needs fresh.please contact SAP" First. The Delicate Art of SAP Note Search How often have you seen a posted message saying "I have searched through SAP Notes and can find nothing related to this matter. Lets use this error message as an example: "BR051I BRBACKUP 6.. or give you new ideas for more search terms to help narrow the scope of my query. If you searched for "Panic! Panic! Panic!" and got no hits. Return to Index. Last. First you could search for the phrase. several things need to be checked: • • • • • • • Is the operating system on the user’s workstation patched to the level recommended by SAP? Is the user using a version of SAPGui that is too old for his workstation? Is the user using a version of SAPGui that is not certified for his operating system? Is the user’s workstation having resource problems? Is the user’s workstation connected to the LAN? Can a different user reproduce the same error on the same workstation? Are there any SAPGui patches that have not been applied? Most SAPGui problems can be solved by either a) deleting and reinstalling SAPGui on the workstation. etc. and search accordingly. you should search the specific error message "BR602W No valid SAP license found".10 (80) BR055I Start of database backup: bdmsqjbi. you could make it even less specific as in "brbackup SAP license error" or "SAP license error". Normally a very specific query will get you the results you need. Since we speak English and we realize that the SAP product was designed and implemented in Germany. . Searching SAP Notes (formerly known as OSS notes) is a science as well as an art.

. and hardware requirements for running SAPGui. add these three lines to the bottom of your \Windows\system32\drivers\etc\services file: sapdp00 sapmsR3I # 3200/tcp 3600/tcp If you have SAP Instances using System Numbers other than 00. QAS. the dispatcher is not reachable. change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS. And. If it still doesn’t go to QAS.11. Open a DOS-Windows and type this: telnet 10. Make sure that these lines were added to the services file on the user’s workstation: After you have successfully configured your SAPGui.com/inbox Read messages from SAP to you .1.11. it means that the RFC_USER doing the ALE communication between the SAP systems is not authorized. If your window never goes completely blank and you set a "Connecting To 10. You might see “You are not authorized to change users in group” or “No authorization for group users in role”.10. check if you are having connection problems due to firewall restrictions.11 3200¬ If the screen rolls and goes totally blank then your dispatcher is reachable. and PRD. Now go to sm59 and do remote logins using the QAS RFC connections. Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. This does not mean that YOU are not authorized. reset the RFC_USER password in DEV. Also.SAP GUI Resources: Hardware and software. something in the RFC setup has changed. You can close the DOS session. Retry your user change... resource. And make sure that the user type is Communication and not dialog. If you have never tested connectivity to a SAP instance on the workstation having the connection problem. see SAP Note 26417 . If you get a logon screen for QAS.. Important SAP Marketplace Links Inbox http://service. Could not open connection to the host. Central User Administration is Not Transferring Change from the CUA Parent Client If CUA stops sending changes from DEV to QAS or PRD.10. first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way. Look for the user you tried to transport but could not. and IP address 10. Either the password or the user type for RFC_USER was changed. you will have to add their equivalents to the services file as well. on port 3200: Connect failed" error message right under the command you entered. or the SM59 RFC connection to was changed and is no longer working.1. If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed.10. be sure that your Insert Key is set so that you can type your password in properly – you can delete whatever is in the password field in order to enter your password. For information regarding operating system. Also. maybe the QAS system is hosed and down. make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct. Return to Index. First..1.. Let’s say your user us trying to connect to System ID (SID) DEV. Return to Index.. System Number 00.sap.

sap.sap.com/serviceconnection Open a Service Connection for to access your SAP landscape Download new images of Installation CDs & DVDs Register Developers and made against SAP objects Add/Change OSS ID user Software Distribution http://service.com/user-admin information . Installation Guides installation Key License Keys http://service.com/swdc SSCR Changes http://service.com/message http://service.com/sscr User Administration http://service.sap.com/dbaora http://service.sap.com/patches Download SAP product guides Request New Permanent License Open problems with SAP An index of SAP links Page for Oracle DBA Search the SAP Notes Database Download SAP software Messages to SAP QuickLinks Page Oracle DBA Page Material OSS Notes Patches patches Remote Connection and Service Connection SAP http://service.com/instguides http://service.com/licensekey http://service.sap.sap.com/remoteconnection Learn about the OSS connection order it from SAP http://service.sap.com/notes http://service.sap.sap.com/quicklinks http://service.sap..sap.sap.

Sign up to vote on this title
UsefulNot useful