P. 1
90959 Basis Operations UNIX Linux

90959 Basis Operations UNIX Linux

|Views: 115|Likes:
Published by rod74can

More info:

Published by: rod74can on Jul 03, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

07/03/2011

pdf

text

original

Sections

  • Starting saprouter (OSS Link)
  • Verifying the Status of saprouter
  • Finding your Hardware Key
  • Generating a Developer’s Key for a Programmer
  • Generating an Object Key to Change a SAP-owned Object
  • Resetting the Cache for a Printer
  • Requesting A New SAP Marketplace User ID aka “S” Number aka OSS ID
  • Checking A New SAP Marketplace User ID aka “S” Number aka OSS ID
  • Adding a New SAP Instance to an Existing TMS Domain Controller
  • Adding a Change Request to a Transport Queue
  • Use Target Groups to Transport to Mulitple Clients in Two Different Instances
  • Configure TMS to Use SAP's Quality Assurance Functionality
  • Automate the Transport Process
  • Copy an Existing User to a New User
  • Activating a User Audit Profile
  • Deactivating a User Audit Profile
  • Deleting a User Audit Profile
  • Creating a Logical System ID to be Assigned to a Client
  • Creating a RFC Connection
  • Modifying a RFC Connection
  • Find your Current SPAM Update and Support Package Level
  • Find your Current Kernel Patch Level
  • Download SPAM/SAINT Updates
  • Download Other SAP Binary Patches
  • Prepare a SPAM/SAINT Update or Support Package for Application
  • Prepare a Kernel Patch for Application
  • Prepare other SAP Binary Patches for Application
  • SAP System Start Up Troubleshooting

.

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?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Automatic recoding of changes – the client can be customized and all changes are generated into change requests. you create the logical system before creating a client so that both start out together. Release 3. .g. no client copy (remote copy) which also selects cross-client customizing objects may be imported into the system. No changes to repository objects – lets users perform client-independent customizing but no development or modifications to repository objects.0 also ensures the following: If there is a productive client in the target system. No changes to client-independent customizing objects . No changes allowed – no modifications can be made to the client – it is protected or locked. to enable adequate protection of a productive client in a system with further (test) clients. posting periods) can always be maintained in a productive client without recording changes. Once you have created a logical system.. No transports allowed – changes are allowed but cannot be transported. inconsistencies may occur in all clients. exchange rates. This is the usual configuration for a production client where customization should not be performed. In a productive client. this means current settings (e.. No changes to repository and client-independent customizing objects – this setting prohibits any client-independent modifications and is common on Production systems.allows for development on repository objects but not client-independent customizing. use the SCC4 transaction to assign the logical system to a client. SAP is planning to link further effective functionality to this flag. Return to Index. If crossclient settings are imported. Normally. customizing settings that can be maintained as "current settings" can be excluded from a client lock or transport links. 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.. * * Customizing client SAP reference client This field should be maintained by the customer for Documentary purposes. 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. Client-Independent Object Changes Changes to repository and client-independent customizing allowed – no restrictions on this client for changes and development. 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.

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

.
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:

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

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

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

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

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

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

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

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

  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 . 5. < 1 second (update) CPU time -. If only few transactions are affected by the performance problem. 4. 6. ST02: Check the buffering quality.. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. Also refer to SAP Note 121625 in this context. 1. 4. 5.     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. ST05: If the database times are high.approx 40% of average response time Wait time -. 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. These tables are your “database hogs”. it should deactivated it in normal operation. What is the utilization of the disks? How high is the paging in the base pool? 4. 2. The sorted results shows the top tables when it comes to rows changes per month. 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. 3. 3. If paging occurs in a buffer. you should additionally note the following points: 1.SM21? Places to look:    2.1 second (dialog). SE30: Carry out a runtime analysis for the affected transactions. ST03: Display the corresponding performance records. To which extent are the hardware resources utilized? Call ST06 at times with poor system performance. 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% of average response time . Check whether modifications were made in the affected or related transactions. Is the total CPU for the last dialog process > 10 minutes? ST04: Is the database monitor activated? If yes. 2. the corresponding parameter should be increased. Look for tables that have experienced unusual monthly growth. ST03: → Select a server → Today's Workload: What are the response times? In the case of poor response times. 3. 6. What is considered “normal” response time? Performance Standards: Response time -.

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

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. like "brbackup No valid SAP license found". and search accordingly. etc. you could search for all words. 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. First you could search for the phrase. you could try "warning message no object header".. or give you new ideas for more search terms to help narrow the scope of my query. If you didn't find a note that matched the problem. current and precise information.. or b) deleting and installing a newer version of SAPGui. If you searched for "Panic! Panic! Panic!" and got no hits.. There are certain notes that you pull over and over again due to some task that needs fresh.10 (80) BR055I Start of database backup: bdmsqjbi. SAPGui Troubleshooting If a user seems to be experiencing SAPGui errors. Since we speak English and we realize that the SAP product was designed and implemented in Germany. and not least.. Why? Because it might contain information leading to other notes that did pertain. you should read the SAP Note even if it didn't look as if it pertained 100%. and if you had no luck. For example. Searching SAP Notes (formerly known as OSS notes) is a science as well as an art.please contact SAP" First..05. If you get at least one hit. ..42 BR602W No valid SAP license found . Return to Index. you should search the specific error message "BR602W No valid SAP license found"."? 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. 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.. read and become familiar with your SAP Notes. Last.anf 2004-02-27 00. Return to Index. you could make it even less specific as in "brbackup SAP license error" or "SAP license error". These are mostly lists of supported printer devices. you could make your next search a little less specifc. known problems with applying patches. 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 that produced nothing tangible. Normally a very specific query will get you the results you need. Lets use this error message as an example: "BR051I BRBACKUP 6. But sometimes things get lost in translation.

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

com/sscr User Administration http://service.sap.com/quicklinks http://service..com/message http://service.sap.com/dbaora http://service.com/notes http://service. Installation Guides installation Key License Keys http://service.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.sap.sap.com/instguides http://service.sap.sap.com/licensekey http://service.sap.sap.sap.com/user-admin information .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/swdc SSCR Changes http://service.sap.sap.sap.com/remoteconnection Learn about the OSS connection order it from SAP http://service.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->