BasisOperations Windows

7/28/2019 BasisOperations Windows

1/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.

Symbol Legend:

Press Enter System ID lower case System ID upper case

How do I....?

Backups

....what do I need to backup?

....how often do I need to backup?

....what are my backup options?

Client Tasks

....add a client?

....add a logical system ID to be assigned to a client?

....change a client?

....copy one client to another in the same R/3 system?

....copy one client to another in different R/3 systems?

....copy only user master data from one client to another?

....delete a client?

....lock a client so configuration changes cannot be made?

....verify that a client copy ran successfully?

....view all past client copies for a client?

Communications Tasks

....add a RFC connection?

....delete a RFC connection?

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

Database Tasks

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

....perform Database Stats, Check Database, and Backup Jobs Oracle?

Job Tasks

....change the start time\date for a scheduled job?

....clean out old job logs?

....delete a scheduled job?

....delete a running job?

....schedule a new job to run?

....verify that a job has run successfully?

Printer Tasks

....add a printer?

....create a new Frontend aka Local aka Desktop Printer?

....reprint a document that has already printed?

....reroute a printer output request?

....reset the cache for a printer?

....view a list of all printer output requests?


2/66

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

Security Tasks

....attach a role to a user?

....attach a user to a role?

....copy an existing role to a new role?

....create a user role?....delete a user role?

....grant a transaction to a user?

....modify a user role?

....move roles from one client to another?

....revoke an authorization from a user?

....revoke a transaction from a user?

Support Package and Binary Patch Tasks

....apply a SPAM\SAINT update?

....apply kernel patches?

....apply other SAP binary patches?

....apply support packages?

....check for New SPAM Updates, Support Packages and Kernel Patches?

....download a kernel patch from SAP Marketplace?

....download a SPAM\SAINT Update?

....download a support package from SAP Marketplace?

....download other SAP binary patches?

....find your Current SPAM Update and Support Package Level

....know when SAP releases new fixes for our SAP software?

....ready a kernel patch for application?

....find SAPs most current patches?

....find your Current Kernel Patch Level?

....find your Current SPAM Update and Support Package Level?

....know when SAP releases new fixes for our SAP software?

....ready a kernel patch for application?

....ready a SPAM\SAINT update or Support Package for application?....ready other SAP binary patches for application?

System Tasks

....add a system parameter?

....apply a SAP (OSS) note?

....check that the system parameters are valid?

....delete a system parameter?

....generate a developers key for a programmer?

....generate an object key to change a SAP-owned object?

....how do I make server files viewable from SAP?

....keep all users out of a transaction?

....modify a system parameter?....open a service connection for SAP to come into my system?

....reclaim system space from obsolete temporary objects?

....recompile all ABAP programs in a R/3 system?

....send a message to all connected users?

....send a message to one connected user?

....start R/3?

....start saprouter (OSS Link)?

....start the OS collector?

....stop a SAP work process?

....stop R/3?

....stop saprouter?


3/66

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

Transport Tasks

....add a change request to a transport queue?

....add a new SAP Instance to an Existing TMS Domain?

....automate the Transport Process?

....configure TMS Transport Management System for the First Time?

....configure TMS to Use SAP's Quality Assurance Functionality?

....re-Transport One or Several Change Requests at Once?

....transport a change from one R/3 system to another?

....transport several change requests at once?

....verify that the transport system is up and running?

....view a history of what changes have been transported?

....use Target Groups to Transport to Mulitple Clients to Different Instances?

User Tasks

....add a user?

....add an ITS user?

....change a users password?

....change several users at once?

....copy an existing user to a new user?

....delete a user?

....delete an ITS user?

....drop a connected user?

....get a list of all users in a client?

....lock a user?

....lock all users at once?

....modify a user?

....modify an ITS user?

....produce various user reports?

....start an audit trace for a specific user?

....view a list of all users currently connected?

Web and Internet Tasks

....start and stop the SAP IGS Server?

Working with the SAP Marketplace

....apply a SAP License Key the new way?

....apply a SAP License Key the old way?

....check the status of a request License Key?

....find your Hardware Key?

....generate a Developers Key for a Programmer?

....generate an Object Key for a Programmer?

....open a Problem via SAP Marketplace?

....open a Service Connection for SAP Support to allow SAP access?

....request a new License Key?


4/66

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

What do I do if....

....my SAP instance wont start?

....my SAPGui session wont start?

....users say response is slow?

....I make user changes in the CUA Parent but they dont show in QAS or PRD?

....a printer has stopped printing?

....I need to apply patches to my SAP instance?

....a support package was applied and now every time a usermoves from one screen to another they get a compilingmessage?

....I downloaded a kernel patch. Now what?

....users are getting errors via the Internet when displaying pictures?

....the development staff says that the IGS server is down?

....a user is receiving multiple X_MESSAGE errors, partialSAPGui screens, SAPLPAD errors when printing, or otherSeemingly SAPGui related errors. What do I do?

....how to find important pages in the SAP Marketplace?


5/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.System Tasks

Starting the SAP Instance

The normal SAP instance start up consists of three parts: starting the SAP OSCollector, starting the Oracle Listener, and starting the SAP instance. The SAPOS Collector (saposcol) and the Oracle Listener (OracleTNSListener) areregistered as Services on your host server during installation so you should not

normally need to start either of these programs. There is also Services calledSAP_ and which must be started.

Even if you have multiple SAP instances on a server, the start up process ispretty much the same. If you have only one SAP instance on ther server, youwill have one saposcol and one OracleTNSListener running as Services. Ifyou have two SAP instances on the same server, you will have one saposcol and twoOracleTNSListeners unless you the database for the second instance wasinstalled as a MCOD or you made major changes to listener.ora and tnsnames.orafiles, either case which allows you to share one listener for multiple instances.If you have multiple listeners due to multiple SAP instances, remember that thekey to having all your SAP instances happy with Oracle is to have each Oracleinstance use a different listener port. The default Oracle is port 1521 duringthe Oracle database instance installation and this is changed to 1527 during the

SAP instance installation. So you want to make sure that your listeners all haveunique listener port numbers like 1527, 1528, 1529, etc. or 1527, 1537, 1547,etc. or whatever works for you and your shop.

If you are running SAP on MS SQL Server, your database engine only needs theMSSQLSERVER Service running plus the saposcol and the SAP_ Servicesin order for your SAP instance to start.

You will only ever have one saposcol program running as this program gathersinformation about things happening on the OS level which pertain to all SAPinstances.

Enough talk, here is how to start a SAP instance.

1. Log on as a user with administrator rights to the server on which your SAPinstance resides.

2. Double-click the SAP MMC console icon of the desktop.3. Open this navigation path: Console Root SAP Systems

.4. Right-click on the and click Start. You can refresh the

Syslog entry until you see the SAP Basis System: Initialization completemessage. Please note, your SAP instance is not fully up until you see thatmessage.

5. Wait until the startup message is seen in the log. Then close the SAP MMCconsole and log off the server.

Return to Index...

Verifying that the SAP Instance is up

The easiest way to confirm that the SAP instance has started successfully is tolog on to the instance. If you try to logon and are refused connection, checkthe logs in the \usr\sap\\DVEBMGS00\work for applicable errors. Sort thefiles in descending order by date. The most helpful files are normally stderr,dev_w0, dev_disp, dev_ms, and dev_rfc.


6/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.If you need further assistance, please refer to the section SAP System Start UpTroubleshooting.

Return to Index...

Stopping the SAP Instance

The stopping of a SAP instance is practically the reversal of the start upProcess; stop the SAP instance, stop the Oracle Listener, and stop the SAP OSCollector. For Windows, you never need to manually stop the database listener,database, and saposcol Services for a normal server cycle. And if there are otherSAP instances still running on the server, the OS Collector needs to continue togather information so leave it up.

1. Log on as a user with administrator rights to the server on which your SAPinstance resides.

2. Double-click the SAP MMC console icon of the desktop.3. Open this navigation path: Console Root SAP Systems

.4. Right-click on the and click Stop. Confirm the

verification popup. You can refresh the Syslog entry until you see the SAPBasis System: Stop Msg Server message. Please note, your SAP instance isnot fully down until you see that message.

5. Wait until the stop message is seen in the log. Then close the SAP MMCconsole and log off the server.

Return to Index...

Starting and Stopping the SAP OS Collector

If for some reason you need to manually start or stop the saposcol program, opena Services session and perform the needed function there.

Return to Index...

Backups

Your Companys Take on Backups

Backup and recovery for a SAP instance is best handled along with the otherbackup and recovery needs of your companys computer systems. But for thosecompanys who do not yet possess a solid backup and recovery solution, or whosimply want to segragate the SAP landscape from all other internal IT solutions,here are a few things you need to know.

Online versus offline, high availability, frequency, are all decisions your IT

staff need to make based on their history with similar procedures at yourcompany, the recommendations of SAP, and the guidance of your implementationBasis consultant. Enforced backups, and detailed and tested recovery proceduresshould be part of any Disaster Recovery plan, and a documented part of any SAPimplementation project.

If your company falls into the latter category, SAP does supply tools for youruses which can be used in either line command form or from within the SAPinstance. If you SAP server contains a tape drive or has access to the networktape unit, transaction DB13 can be used to schedule periodic backups. This isthe same transaction where weekly statistics, log cleanup, and databaseverification jobs are scheduled in the post-installation work after installation


7/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.of a new SAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed incommand line form by the IT staff.

For more information, please see the SAP Online Documentation for DB13 by goingto the DB13 transaction and clicking Help Application Help or referring to thesection Creating Database Statistics, Index Rebuilds, and Log Backup Jobs Oracle.More information regarding BRCONNECT can be found in the SAP BRCONNECTGuide which can be found at http:\\service.sap.com\instguides.

Return to Index...

What Needs to Be Backed Up?

The PRD Instance

Daily backup should be made for these SAP specific directories:

\usr\sap\\usr\sap\trans on the TMS Domain Controller ServerAny directories containing flat files that are used by the SAP instance

Daily backups should be made for these Oracle specific directories:

All \oracle\ directoriesDirectory holding redo logs if not in the \oracle\ structure

Daily backups should be made for these MS SQL Server specific directories:

All \>SID>Datax directoriesAll \>SID>Logx directories

Weekly backup should be made for these OS specific directories:

The c: drive

The registryThe hard disk mapping

For Oracle, the entire \oracle directory should be backed up daily if there isonly one Oracle Instance on the server, and each separate \oracle\ directoryif there is more than one instance on the server. If MS SQL Server, the data andlog files must be backed up.

It is also recommended that a full offline image of the entire server be madebefore the monthly closing cycle.

The DEV and QAS Instances

Weekly backup should be made for these SAP specific directories:

\usr\sap\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

Weekly backups should be made for these MS SQL Server specific directories:

All \>SID>Datax directories
http://service.sap.com/instguideshttp://service.sap.com/instguides


8/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.All \>SID>Logx directories

Monthly backup should be made for these OS specific directories:

The c: driveThe registryThe hard disk mapping

For Oracle, the entire \oracle\ directory should be backed up daily if thereis only one Oracle Instance on the server, and each separate \oracle\directory if there is more than one instance on the server. If MS SQL Server,the data and log files must be backed up.

It is also recommended that a full offline image of the entire server be made atthe same time every month.

Return to Index...

Working with saprouter

Starting saprouter (OSS Link)

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

Return to Index...

Verifying the Status of saprouter

If you have previously successfully established SAPNet (OSS) communications withSAP via saprouter in the past, there can only be three reasons for a broken

SAPNet connection to SAP: the SAP VPN is down (which rarely happens); yoursaprouter configuration has been incorrectly changed (also very rare); or yoursaprouter is not running (happens all the time).

1. Log on to the appropriate server as adm.2. Click Start Administrative Tools Services to open a Services window.3. Look at the SAPROUTER service. If is not started, right-click to start the

service. If it is started, right-click & Stop the service and then right-click & Start the service. This should bounce your saprouter instance.

4. You may now log off the server.

Return to Index...

Stopping saprouter

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

Return to Index...


9/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Applying a SAP Note

Not all SAP Notes can be applied via the SNOTE transaction. Some are informationonly, providing no code corrections. Others entail corrections that can only bedone manually. This latter type of SAP Note should be applied to your SAP systemin conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTEchange requests NOT be transported into other systems. Use the SNOTE transactionin each SAP system that needs the correction, and delete the generated change

requests since they should never be transported and could lock resources duringapplication of other SAP Notes and support package application.

If you do not have a working OSS connection, you can download an OSS note fromthe SAP Marketplace using the SAP Download Manager and use the upload feature inSNOTE to load it into the SAP instance instead.

1. Log on to client 000 in the appropriate SAP system.2. Go to transaction SNOTE.3. On the Note Assistant - Version XXX\XXXX: Worklist screen, on the top-most

menu bar click Goto SAP Note download.4. On the Note Assistant: Download Note popup, type the number of the SAP note

in the Note numberbox and click the clock picture-icon. A SAP Note XXXXXXis being downloadedmessage will appear in the bottom status bar. If youget a communications error message, verify that saprouter is up and tryagain.

5. Once the SAP Note has been downloaded, it will appear on the Assistant -Version XXX\XXXX: Worklist screen under the SAP Notes New navigation tree.The SAP Note can only be applied if there is a blue box with a black arrowto the left of the note number. If there is a gray diamond instead, thedownloaded note cannot be applied or is not application for this SAP system.

6. To apply the SAP Note, on the Note Assistant - Version XXX\XXXX: Worklistscreen double click on the downloaded SAP Note number.

7. On the Note Assistant Display Note XXXXXXscreen, read the note text tosee if there are any necessary manual tasks to be performed after the noteis applied. When you are ready to apply the note, click on the clockpicture-icon.

8. If there are any prerequisite SAP Notes which need to be applied to the SAPsystem before the downloaded SAP Note can be applied, a list will appear ina Load the following notes into your SAP system popup will appear. Clickthe clock picture-icon to download these prerequisite SAP Notes as well. Ifany of the prerequisite SAP Notes must be applied in parallel with theoriginal downloaded SAP Note, a list will appear in a SAP Note queue to beImportedpopup. Click the clock picture-icon to apply all the listed SAPNotes.

9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Noteread popup will appear. Once you have read the information contained inthis popup, click the Yes button.

10. A standard Make repairs in foreign namespaces... popup will appear. Clickthe green to continue.

11. On the Prompt for transportable Workbench request popup, click the blankpage picture-icon to create a new change request. On the Create Requestpopup, fill in the Short description and click the Save picture-icon. Youwill be returned to the Prompt for transportable Workbench request popupwhich contains the generated change request number for this system change.Click the green to continue.

12. On the Confirm changes popup, click the green to continue.13. After the SAP Note has been applied to the SAP system, you will be returned

to the Note Assistant - Version XXX\XXXX: Worklist screen. There is nocompletion message. Click the green and pencil picture-icon.

14. On the Set Processing Status for Note XXXXXXpopup, click on the Completedline to turn on the radio button. Click the green . You can now leave


10/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.the SNOTE transaction. Modified programs, functions, etc. may requirerecompilation.

15. If the OSS note you applied changed a ABAP program, you must go to the SE38transaction and manually recompile the program. If it changed a function,go to transaction SE37 and click the Single Test button this is enough toforce the function to rebuild and you can back out of the SE37 transaction.

Return to Index...

Working with the SAP Marketplace

When a SAP instance is first installed, it comes with an automatical four weeklicense. But you cant install any kind of SSCR key on a termporary instance, soit is best to get the permanent license key immediately.

The license key request process has been drastically overhauled by SAP over thepast. Normally, if you request a new SAP license key, the information will be e-mailed to you in the form of a script. But in case you dont receive this e-mailpromptly, it is important to know how to obtain the newly generated key the old-fashioned way.

Finding your Hardware Key

1. Log on to the server containing the new SAP system as adm.2. Open a DOS-prompt window and type the following, pressing enter when you are

done:

saplicense -get

3. You will see a line reading saplicense: HARDWARE KEY = XXXXXXXXXXXXXX.Make note of this information before pressing Enter.

4. You may now close the DOS-prompt window and log off the server.

Return to Index...

Alternative Method for Finding your Hardware Key

1. Log on to client 000 of the newly installed SAP system.2. Go to transaction SLICENSE.3. From the top-most menu bar of the SAP License Administration screen, click

Goto Get hardware key.4. On the Determine Remote Hardware Keypopup, find the host name or IP address

for the new SAP system server. Click the button to the left of this entryto high-bright the line. Click the Detrmne button to continue. Thehardware key will appear in the box to the right of the Detrmne button.

5. You may now leave the SLICENSE transaction.

Return to Index...

Requesting a New SAP License Key

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\licensekey.

2. In the navigator tree on the right-hand side of the License Keys screen,click on mySAP Business Suite.

3. On the License keys for mySAP Business Suite screen, click on the Requestlicense keyhyperlink.
http://service.sap.com/licensekeyhttp://service.sap.com/licensekey


11/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.4. On the License key: Request screen, click the correct Installation hyperlink

the mySAP Business Suite component.5. On the License key request: System overviewscreen, click the New system

button.6. On the License key: Request for a new system screen, fill in the required

information in the System section. In the License request section, fill inthe Hardware keybox right above the Save New Item button. After you havesupplied the hardware key, click the Save New Item button. The license key

request will be shifted up to the first line of the License request list.Click on the to the left of the license request to place a in the box.Now you are finally ready to click the Send Request button.

7. You may now close your web browser session.

Return to Index...

Checking the Status of a Requested SAP License Key

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\licensekey.

2. In the navigator tree on the right-hand side of the License Keys screen,click on mySAP Business Suite.

3. On the License keys for mySAP Business Suite screen, click on the Displaylicense keys requested by me hyperlink.

4. On the License key: request screen, look for your requested key. It shouldappear with the you provided during the request process. If theStatus shows as Sent to SAP, the license key has not yet been generated. Ifthe Status shows as Completed, your new license key has been generated andyou can click on the System hyperlink to continue.

5. On the License key: request screen, scroll down until you can see theLicense request section. Under the License keyheader you will see you newSAP system license key. Write this key down and remember that it is casesensitive. Or you can cut-and-paste it to a more convenient storagelocation.


Return to Index...

Applying a SAP License Key the Old Way

1. Log on to the server that contains the new SAP system as adm.2. Open a DOS-prompt and type:

saplicense -install

3. You will be prompted for the , hardware key, expiration date of the newlicense, and the new license. Press Enter after the entry of each piece of

data.4. Once the new license key has been accepted, you will received a License key

appliedmessage. If you have the TXT file SAP e-mailed you, you can placeit somewhere on your server and use the following syntax to install thelicense as well:

saplicense install ifile=

4. You may now log off the server.

Return to Index...
http://service.sap.com/licensekeyhttp://service.sap.com/licensekey


12/66


Applying a SAP License Key the New Way

1. Log on to client 000 in the SAP system in which the new license key is to beinstalled.

2. Go to transaction SLICENSE.3. From the top-most menu bar on the SAP License Administration screen, click

Edit Install license.

4. On the Install New License popup, fill in the new license key you obtainedfrom SAP. Click network picture-icon to finish the new licenseinstallation.

5. You will receive a License key successfully installedmessage. You may nowleave the SLICENSE transaction.

Return to Index...

Generating a Developers Key for a Programmer

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\sscr.

2. In the navigator tree on the right-hand side of the SSCR screen, click onRegistration.3. On the SSCR Registration screen, click the Register developerradio button

and click an Installation hyperlink. Make sure you select the correctInstallation Number for the SAP flavor you need or the generated key willnot work.

4. On the SSCR Register Developerscreen, type in the developers SAP user IDand click the Registerbutton.

5. A new Details section will appear. Note the generated developers key orcut-and-paste for other storage.


Return to Index...

Generating an Object Key to Change a SAP-owned Object

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\sscr.

2. In the navigator tree on the right-hand side of the SSCR screen, click onRegistration.

3. On the SSCR Registration screen, click the Register object radio buttonand click an Installation hyperlink. Make sure you use the MS SQLinstallation and not R/3.

4. On the SSCR Register Object screen, fill in the information necessary togenerate an object key. If you need help, this information is contained inthe Register Object popup the programmer received on his workstation. Or,if this is a repair, the information can be found in the SAP Note containingthe advanced correction. Click the Registerbutton once all information hasbeen enter.

5. A new Details section will appear. Note the generated object key or cut-and-paste for other storage.


Return to Index...

Opening a Service Connection for SAP Support
http://service.sap.com/sscrhttp://service.sap.com/sscrhttp://service.sap.com/sscrhttp://service.sap.com/sscr


13/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Before opening a service connection for SAP, be sure that the SAPAG client hasbeen added to the appropriate SAP system and Client, and that a Security AuditTrace has been activated for the SAPAG ID.

Before a Service Connection to a SAP server via your saprouter can be created,the saprouter must run the LOP Line Opener Program to initiate the mode ofSAP connection. Please LOPInstalltion.exe on your saprouter server before tryingto add and open any Service Connections.

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\serviceconnection.

2. On the Service Connections screen, click the Service Connections button.3. On the Service Connections Overview screen, scroll down the page and find

the SAP instance you want to open. Click on the red X in that instancesline.

4. In the Enter Data for the systems semi-automatic opening popup, set thedays, hours, and minutes you want the service connection to stay open.Click the Continue button.

This part is being rewritten to meet the new SAP procedures.

Return to Index...

Problem Logging with SAP Support

Reporting a Problem to SAP

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\message.2. On the Create Customer Messages screen, click on the Start Message Wizard

button.3. On the Customer messages Create screen, click the Select a System button.4. On the System Selection popup, click on the + sign next to Show systems to

see a list of your SAP systems registered with SAP. From the expanded list

of system, click on the radio button just left of the for which youare reporting the problem. Click the Choose button and you will bereturned to the Customer messages Create screen.

5. On the Customer messages Create screen, click on the radio button to theleft of the System type which has the problem: development system, testsystem, orproduction system. From the Release dropdown, select theappropriate SAP software release. Click the Continue hyperlink.

6. On the next Customer messages Create screen, scroll down to the bottom ofthe screen. If the problem involves an add-on, select the appropriate Add-on and Add-on release from the dropdowns; if an add-on is not involved,leave these dropdowns blank. Verify that the information showing in theOper. System, Database, and Frontenddropdowns is correct. If it is notcorrect, selection your SAP systems information from the appropriate

dropdowns. Click the Continue hyperlink.7. On the next Customer messages Create screen, scroll down to the bottom of

the screen. From the Prioritydropdown, select the appropriate priority ofLow, Medium, High, or Very High. From the Component dropdown, select whichSAP component is having the problem. Once you select a component, asecondary Component dropdown will appear. Select a secondary component anda third component as well. Do the best you can to make all three componentpieces fit your problem as closely as possible. Click the Continuehyperlink.

8. On the next Customer messages Create screen, scroll down to the bottom ofthe screen. Select a language from the Language dropdown, type a short but
http://service.sap.com/serviceconnectionhttp://service.sap.com/messagehttp://service.sap.com/serviceconnectionhttp://service.sap.com/message


14/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.descriptive summary of your problem in the Short description box, and typea more detailed description of your problem in the Long test box.

9. If there are logs or other files which might assist SAP in resolving theissue, rename them all so that they have a suffix of .log and use the Addattachment hyperlink and the Attachments popup to attach them to themessage. After attaching all the necessary files, click the Closehyperlink to return to the Customer messages Create screen.

10. When you have provided as much information as possible, click the Send to

SAPhyperlink.11. You will receive a confirmation screen with a generation problem number.Write this problem number down for later use.

12. You may now leave the Message Wizardand close the web browser window.

Return to Index...

Checking the Status of a Reported Problem

1. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\message.2. Click on Customer Messages. All the open OSS problems you have sent to SAP

will appear here.3. You may now leave the Message Wizardand close the web browser window.

Return to Index...

Creating, Modifying, Deleting, Transporting, and Resetting Print Devices

Creating a Print Device

1. Log on to any client in the appropriate SAP system.2. Go to transaction SPAD.3. On the Spool Administration: Initial Screen screen,under the

Devices\servers tab click the Output devices button.

4. On the Spool Administration: List of Output Devices screen, click the pencilpicture-icon to switch into change mode. The easiest way to create a newprinter is to copy an existing one. Click on a similar printer in theoutput devices screen then click the create with template picture-icon.

5. On the Spool Administration: Create Output Device screen, fill in the Outputdevice and Short name. Make any changes that are unique for the new printeron the Device Attributes and Host Spool Acc Methodtabs. When all therequired data has been changed\added, click the Save picture-icon.

6. You will receive an Output device was savedmessage in the status bar at thebottom of the screen. Click the lit match picture-icon to activate theprinter.

7. You may now leave the SPAD transaction.

Return to Index...

Modifying a Print Device


Devices\servers tab click the Output devices button.4. On the Spool Administration: List of Output Devices screen, click the pencil

picture-icon to switch into change mode. Double click on the output deviceto be changed.
http://service.sap.com/messagehttp://service.sap.com/message


15/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.5. On the Spool Administration: Output Device (Change) screen, make any

necessary changes on the Device Attributes and Host Spool Acc Methodtabs.When all the required data has been changed\added, click the Save picture-icon.

6. You will receive an Output device was savedmessage in the status bar at thebottom of the screen. Click the lit match picture-icon to activate theprinter.


Return to Index...

Deleting a Print Device


Devices\servers tab click the Output devices button.4. On the Spool Administration: List of Output Devices screen, click the pencil

picture-icon to switch into change mode. Click on the output device to bedeleted and then click the trash can picture-icon.

5. On the Spool admin.: Delete screen, verify that the correct printer is aboutto be deleted. Click the Yes button.6. You will receive an Output device deletedmessage in the status bar at the

bottom of the screen. You may now leave the SPAD transaction.

Return to Index...

Transporting a Printer or a Group of Printers


Devices\servers tab click the Output devices button.4. On the Spool Administration: List of Output Devices screen, click the pencilpicture-icon to switch into change mode.

5. Click on an output device to be transported and then click the truckpicture-icon.

6. On the Spool Administration: List of Output Devices (Change) popup, clickthe green picture-icon.

7. On the Prompt for Workbench request popup, click the blank page picture-iconto create a new change request. On the Create Request popup, fill in theShort description and click the Save picture-icon. You will be returned tothe Prompt for transportable Workbench request popup which contains thegenerated change request number for this system change. Click the green tocontinue.

8.You will receive an Entry is made in transport request message in the statusbar at the bottom of the screen. Repeat steps 11 through 14 as many timesas necessary, using the same transport request for all printers.


Return to Index...

Resetting the Cache for a Printer

If resetting the printer cache does not clear your printing problem, try usingsome a non-SAP application to print to it to see if it working correctly on thenetwork. This should at least narrow down the possibilities.


16/66



Devices\servers tab click the Output devices button.4. On the Spool Administration: List of Output Devices screen, double click on

the printer you need to reset.5. On the Spool Administration: Output Device (Display) screen, click on the

pencil picture-icon to switch from display mode to change mode.6. On the Administration: Output Device (Change) screen, on the top-most menu

bar click Edit Reactivate.7. On the same Administration: Output Device (Display) screen, on the top-most

menu bar click Edit Reset Cache.8. On the same Administration: Output Device (Display) screen, on the top-most

menu bar click Edit NI Reset.9. You may now leave the SPAD transaction.

Return to Index...

Printer Output

Creating a Local aka Frontend Printer aka Desktop Printer

Local or frontend printing is sometimes confusing in concept but actually veryeasy to understand. As a rule, localprinter is simply another way of saying thatthe user is going to print to the defaultprinter designated on his\herworkstation. You probably do this all the time with Windows toprinterspreadsheets, Word documents, etc without thinking about it. You can do the samething using SAP.

1. Log on to any client in the appropriate SAP system.2. Go to transaction SPAD.3. On the Spool Administration: Initial Screen screen, click the Output Devices

button.4. On the Spool Administration: List of Output Devices screen, click the

Change button and then the Create button.5. On the Spool Administration: Create Output Device screen, fill in the Output Name and Short name - I normally use a short name of DESK for Desktop Printing but alot of people use a Short name SWIN or LOCL

as well. Use the following DeviceAttributes fields:

Device type = SWINDevice Class = standard printer

And the following Access Methodfields:

Host spool access method= F: Printing on frontend computerHost printer= __DEFAULT. That is _ _ D E F A U L T

Save the printer.6. You may now leave the SPAD transaction.

Using this printer will cause print to go to SAPLPD which will use the defaultprinter of the current workstation.

Return to Index...

Viewing a List of Pending Printer Output Requests for All Printers


17/66


1. Log on to any client in the appropriate SAP system.2. Go to transaction SP01.3. On the Output Controller: Spool request selection Screen screen,click on

the Output requests tab.4. On the Output Controller: Output request selection Screen screen, fill in

any information needed to filter the selection results. Then click on theclock picture-icon.

5. A list of all pending output requests will be displayed.6. You may now leave the SP01 transaction.

Return to Index...

Viewing a List of Output Requests for a Specific Printer


Devices\servers tab click the Output devices button. On the SpoolAdministration: List of Output Devices screen, click on the printer where

you need to check the output requests. Then click on the printer and pagepicture-icon.4. A list of all pending output requests for the selected printer will be

displayed.5. You may now leave the SPAD transaction.

Return to Index...

Reprinting a Document

1. Log on to any client in the appropriate SAP system.2. Go to transaction SP01.

3. On the Output Controller: Spool request selection Screen screen,fill in anyinformation needed to filter the selection results. Then click on the clockpicture-icon.

4. A list of all spool requests will be displayed. Double click on the spoolrequest that is to be reprinted.

5. Click on the printer picture-icon. An Output request createdmessage shouldappear in the bottom status bar.

6. You may now leave the SP01 transaction.

Return to Index...

Re-routing Print to a Different Printer

1. Log on to any client in the appropriate SAP system.2. Go to transaction SP01.3. On the Output Controller: Spool request selection Screen screen,fill in any

information needed to filter the selection results. Then click on the clockpicture-icon.

4. A list of all spool requests will be displayed. Double click on the spoolrequest that is to be reprinted.

5. Click on the printer with a box outline picture-icon. On the Outputcontroller: Print spool request XXXXscreen, tab down to the line readingOutput device and select a new printer. Click on the printer picture-icon.

6. On the Output control: Save attributes popup, click the Yes button.


18/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.7. On the Confirm redirection of output popup, click the Yes button. An Output

request createdmessage should appear in the bottom status bar.8. You may now leave the SP01 transaction.

Return to Index...

Deleting Obsolete Temporary Objects and Reclaiming the Space

1. Log on to any client in the appropriate SAP system.2. Go to transaction SP12.3. On the TemSe --- Administration of Temporary Sequential Data screen, on the

top-most menu bar click TemSe database Reorganization.4. On the TemSe --- Administration of Temporary Sequential Data popup, click

the All TemSe objects older than option to turn on the radio button to theleft. Fill in the Days box with 7 for development and quality assurancesSAP systems, and 32 in production SAP systems. Click the Delete button.

5. On the TemSe objects older than XX days popup, click the Yes button.6. After the successful deletion of the selected temporary objects, you will be

returned to the TemSe --- Administration of Temporary Sequential Datascreen. There is no task completion message.

7. You may now leave the SP12 transaction.

Return to Index...

Mass Recompilation of ABAP Programs

1. Log on to any client in the appropriate SAP system.2. Go to transaction SGEN.3. On the SAP Load Generatorscreen - Generation task section, click on the

line reading Generate all objects in selected software components to turnon the radio button to the left. Click on the Continue button at thebottom.

4. On the SAP Load Generatorscreen - Selection by software components ofgeneration set section, click the button to the left of each entry listed inthe Software component box. Click the Continue button at the bottom of thescreen.

5. On the SAP Load Generatorscreen Select server for parallel generationsection, there should only be one entry in the Serverbox. Click the buttonto the left of this entry. Click the Continue button at the bottom of thescreen. Several messages will appear in the bottom status bar before thenext screen appears.

6. On the SAP Load Generator Job Monitorscreen, fill in the time and datelisted under the Schedule job at button located at the bottom of the screen.Click on the Schedule job at button.

7. On the SAP Load Generator Job Monitorscreen Load generator status

section, the status of mass generation is shown. You may now leave the SGENtransaction and later return to check the progress of the recompilation. Noother load regeneration jobs can be scheduled until this one completes. Ifa load regeneration jobs fails for some reason, return to the SGEN screenfor instructions on how to restart the job.

Return to Index...

SAP IGS Server


19/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.The IGS server (Internet Graphics Server) component displays and generates thegraphics used by SAPGui HTML users. For example, the BW users accessing reportsvia the internet use the IGS server. The ITS server also channels graphicsthrough the IGS server. The IGS server is installed as a started Service on eachserver so starting and stopping this service can be done using the Servicessession on the SAP server.

The most current installations of SAP use the START profile of the SAP instanceto start the IGS server and it appears as a process in the Process List of theSAP MMC Console.

Return to Index...

Support Tasks in the SAP Marketplace

Some adminitrative tasks performed on the SAP Marketplace areinstantaneous such as SSCR (SAP Source Correction Registration)requests for Developer and Object Key, while others like apermanent license key request or registeration of a new OSS ID,can take 15 minutes, or several days. As you work with thevarious SAP provided tools, you will learn the difference between

normal lag time, and the possibility of something being wrong.

Requesting A New SAP Marketplace User ID aka S Number aka OSS ID

1. You will need the first and last name, function, department, departmenttitle, language, telephone number, language, and email address of theperson(s) being added as these are all required fields.

2. Log on to the SAP Marketplace using an OSS ID with Administration rights http:\\service.sap.com\user-admin.

3. From the left navigational tree, click on Maintain User Data Request newusers. You may be asked for your OSS ID and password again, dependently onyour point of original logon.

4. On the User Data Maintenance screen, fill in the gathered information from

step #1. Then press Save. You may or may not receive a confirmationmessage.

5. You may now log off the SAP Marketplace.

Return to Index...

Checking A New SAP Marketplace User ID aka S Number aka OSS ID


2. From the left navigational tree, click on Maintain User Data Displayrequested users. You may be asked for your OSS ID and password again,

dependently on your point of original logon.3. On the User Data Maintenance screen, you will see a list of your mostly

recently generated OSS IDs. If the user ID you are seeking does not appearon the screen, you can fill in any of the information allowed in the top rowto performa a search.

4. Verify the status of the OSS ID for which you are looking. If the Statusreads Successful, and both the User IDand Initial Passwordfields containlegitmate data, your OSS ID has been generated and you can pass theinformation on to your user.If the Status reads Requesting, your OSS ID has not been generated socome again later to check the status. If the Status makes reference to some
http://service.sap.com/user-adminhttp://service.sap.com/user-adminhttp://service.sap.com/user-adminhttp://service.sap.com/user-admin


20/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.type of error condition, please open an OSS problem to get it resolved. Thenormal turnaround for an OSS ID generation is eight hours or less.


Return to Index...

Changing the Authorizations for an Existing SAP Marketplace User IDaka S Number aka OSS ID

***The vast majority of your OSS ID users have enough privileges toperform their SAP Marketplace tasks without any additional rightsgranted to their user ID.


2. From the left navigational tree, click on Maintain User Data Search andmaintain users. You may be asked for your OSS ID and password again,dependently on your point of original logon.

3. On the User Data Maintenance screen, click Search for an entire list of yourSAP Marketplace users, or fill in the provided fields to help narrow yoursearch, pressing Search when you are ready.

4. From the second User Data Maintenance screen, click on the Surname of anyuser you wish to change.

5. On the next User Data Maintenance screen, click on the Authorizations tab,and then click the Edit button on the bottom of the displayed section.

6. From the resulting User Data Maintenance Authorization objects overviewscreen, click on a line you want to change. For example, if you want theOSS ID to be able to create new OSS problems with SAP, click the CreateCustomer messages on box at the far left to the line.

7. On the resulting User Data Maintenance Create Customer messages screen,click on your option Customer if you want the user to be able to openproblems for any SAP Instance you own, or select a specific Installation(s)for only, say, CRM instances.

8. Click the Add button at the bottom of th page, and you will be returned tostep #6. Repeat as many times as you need to do so in order to change theOSS ID to your requirements.

9. When all the changes have been completed, make sure you are at the samescreen as in step #6 and click Save. You should get a screen thanking youand saying that your changes have been saved.


Return to Index...

Creating, Modifying, and Deleting System Parameters

Creating System Parameters

1. Log on to any client in the appropriate SAP system.2. Go to transaction RZ10.3. On the Edit Profiles screen, select the _DVEBMGS00_SAP Profile

from the dropdown, or whatever instance profile you need to change. In theEdit profile section, click the radio button to the left of Extendedmaintenance. Click the Change button.

4. On the Maintain R/3 Profile screen, click the Add Parameterbutton.5. On the next Maintain R/3 Profile screen, type in the new Parameter name and

Parameter val. Click the Copybutton. Click the white arrow on greenpicture-icon twice.
http://service.sap.com/user-adminhttp://service.sap.com/user-admin


21/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.6. On the Maintain R/3 Profile popup, click the Yes button to save your

changes.7. On the Edit Profiles screen, click the Save picture-icon.8. On the Save profile popup, click the No button.9. On the Activate profile popup, click the Yes button.10. On the Edit Profiles popup, click the green button.11. On the Caution! Caution! Caution! popup, click the green button.12. If you receive a Possible Inconsistencies in OP Modes screen, double click

over the unless you are unsure of why this message has been displayed.13. You will not get a confirmation message. You may now leave the RZ10

transaction.

Return to Index...

Modifying System Parameters


from the dropdown, or whatever instance profile you need to change. In the

Edit profile section, click the radio button to the left of Extendedmaintenance. Click the Change button.

4. On the Maintain R/3 Profile screen, locate the parameter that needs to bechanged in the Parameter name column. Change the matching value underParameter value to the new value. Click the Copybutton. Click the whitearrow on green picture-icon.

5. On the Edit Profiles screen, click the Save picture-icon.6. On the Save profile popup, click the No button.7. On the Activate profile popup, click the Yes button.8. On the Edit Profiles popup, click the green button.9. On the Caution! Caution! Caution! popup, click the green button.10. If you receive a Possible Inconsistencies in OP Modes screen, double click

over the unless you are unsure of why this message has been displayed.

11. You will not get a confirmation message. You may now leave the RZ10transaction.

Return to Index...

Deleting System Parameters


from the dropdown, or whatever instance profile you need to change. In theEdit profile section, click the radio button to the left of Extended

maintenance. Click the Change button.4. On the Maintain R/3 Profile screen, locate the parameter you need to delete

and click on the Parameter name to high-bright it. On the top-most menubar, click Parameter Delete.

5. On the next Maintain R/3 Profile popup, make sure that the parameter listedis the one you need to delete. Click the Yes button to delete theparameter. You will receive a Parameter was deletedmessage in the statusbar at the bottom of the screen. Click the Copybutton. Click the whitearrow on green picture-icon.

6. On the Edit Profiles screen, click the Save picture-icon.7. On the Save profile popup, click the No button.8. On the Activate profile popup, click the Yes button.


22/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.9. On the Edit Profiles popup, click the green button.10. On the Caution! Caution! Caution! popup, click the green button.11. If you receive a Possible Inconsistencies in OP Modes screen, double click

over the unless you are unsure of why this message has been displayed.12. You may now leave the RZ10 transaction.

Return to Index...

Overview of All Work Processes Running on a SAP System

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM50.3. On the Process Overviewscreen, all processing threads for the SAP system

are displayed. If a thread is being used, the name of the report runningwill be displayed as well as the number of seconds that the report has beenrunning, the client in which the report is running, the action the report iscurrently doing, and, if applicable, the table the report is currentlyaccessing.

4. Click on the blue arrow circle picture-icon to refresh the process dataappearing on the screen.

5. Click the white clock picture-icon to display the amount of CPU timeconsumed by each process thread so far.6. Double click any display line containing a report name in order to see more

detailed information about the running report. This information includesdatabase access statistics and timings. Use the white arrow on greenpicture-icon to go back to the Process Overviewscreen.

7. Click on any process thread and then click the blue cylinder with glassespicture-icon. This will display the Trace Data screen which shows theactual communication between SAP, the operating system, and the databaseserver. This information is useful when tracking process thread problems.Use the white arrow on green picture-icon to go back to the Process Overviewscreen.

8. You may now leave the SM50 transaction.

Return to Index...

Stopping Run-Away or Bad Work Processes

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM50.3. On the Process Overviewscreen, find the process which must be

stopped. Place a in the to the left of the process numberto be stopped by pressing Space. On the top-most menu bar,click the Process Cancel without core.

4. Click the blue arrow circle picture-icon to refresh the ProcessOverviewscreen until the stopped process has cleared from the

display.5. You may now leave the SM50 transaction.

If this does not kill the process, you can go to transaction SM04 and kill theusers session. If this does not kill the process, you can log on to the server,open a Task Manager session, and End the Process. If this does not kill thesession, there is an executable in the RUN directory on the server calledsapntkill.exe. Run it providing the process ID number. If none of the abovework, you have no choice but to bounce the SAP instance and\or possibly theserve.

Return to Index...


23/66


Increasing or Decreasing the Number of Work Processes

1. Log on to any client in the appropriate SAP system.2. Go to transaction RZ10.3. On the Save profile popup, click the No button.4. On the Edit Profiles screen, select the _DVEBMGS00_SAP Profile

from the dropdown, or whatever instance profile you need to change. In theEdit profile section, click the radio button to the left of Extendedmaintenance. Click the Change button.

5. On the Maintain R/3 Profile screen, locate the dialog processesrdisp\wp_no_dia line in the Parameter name column. Change the matchingvalue under Parameter value to the new value. Click the Copybutton. Do thesame for the batch processes, rdisp\wp_no_btc, and the update processes,rdisp\wp_no_vb. Be sure to click the Copybutton after each change. Whenall the changes have been made, click the white arrow on green picture-icon.

6. On the Edit Profiles screen, click the Save picture-icon.7. On the Save profile popup, click the No button.8. On the Activate profile popup, click the Yes button.9. On the Edit Profiles popup, click the green button.

10. On the Caution! Caution! Caution! popup, click the green button.11. If you receive a Possible Inconsistencies in OP Modes screen, double click

over the unless you are unsure of why this message has been displayed.12. You will not get a confirmation message. You may now leave the RZ10

transaction.

Return to Index...

Broadcasting System Messages

Creating a System Message

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM02.3. On the System Messages screen, click the Create button.4. On the Create System Messages popup, type up to 3 lines of System message

text. Select a server (there should only be one) from the Serverdropdown.If you want to limit the message to one client, select a client from theClient dropdown. If desired, fill in an Expiry date and\or Delete date.Click the green to save the message.

5. A System message addedmessage will appear in the bottom status bar. Youmay now leave the SM02 transaction.

Return to Index...

Modifying a System Message

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM02.3. On the System Messages screen, double click on the Idnumber of the message

that needs to be changed.4. On the Display System Messages popup, click the pencil and glasses picture-

icon to switch to change mode.5. On the Change System Messages popup, make your changes and click the green

to save the changed message.


24/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.6. A System message changedmessage will appear in the bottom status bar. You

may now leave the SM02 transaction.

Return to Index...

Deleting a System Message

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM02.3. On the System Messages screen, click on the Idnumber of the message to

highlight the message that needs to be deleted. Click the Delete button.4. On the System message: Delete popup, click the Yes button to delete the

message.5. A System message deletedmessage will appear in the bottom status bar. You

may now leave the SM02 transaction.

Return to Index...

Sending a System Message to a Single User

1. Log on to any client in the appropriate SAP system.2. Go to transaction SE37.3. On the Function Builder: Initial Screen screen, type in the Function name

TH_POPUP. Click the Single Test wrench picture-icon.4. On the Test Function Module: Initial Screen screen, fill in User, Client,

and Message Text. Click the clock picture-icon. The message will be sentto the specified user.

5. You may now leave the SE37 transaction.

Return to Index...

Locking R/3 Transactions

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM01.3. On the Transaction Code: Lock\Unlock screen, you will see an empty box at

the very bottom of the screen. Type in the transaction code you want tolock and press Enter.

4. The transaction code to be locked should appear at the top of thetransaction list. Place a in the to the left of the transaction to belocked by pressing Space. Press Enter.

5. The transaction is now locked. You may now leave the SM01 transaction.

Return to Index...

Short Dump Analysis

Short dumps care generated when one of the SAP programs encounters an abnormalcondition, a condition that the program was not coded to handle in any of itserror routines. While it is not a function of the Basis support team to debugSAP programs, familiarity with some of the dump sections can be valuable for SAPNote searches and\or logging system problems with SAP.

1. Log on to any client in the appropriate SAP system.


25/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.2. Go to transaction ST22.3. On the ABAP runtime errors screen, you can click the Todaybutton for

todays dumps, the Yesterdaybutton for yesterdays dumps, or use the OwnSelection section of the screen to narrow down your time date\time range andthen click the Start you selection button.

4. On the List of Selected Runtime Errors screen, double-click on any shortdump you want to examine more closely.

5. On the Runtime Error Long List screen, make note of the error that occurred

in the What Happened? section, any unique information in the Error analysissection, and search terms for searching SAP Notes in the How to correct theerrorsection.

6. You may now leave the ST22 transaction.

Return to Index...

Viewing Database Lock Information

1. Log on to any client in the appropriate SAP system.2. Go to transaction DB01.3. The information displayed on the Oracle Lock Monitor screen can be sorted

and filtered to meet your reporting requirements.4. You may now leave the DB01 transaction.

Return to Index...

Viewing Table Lock Information

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM12.3. On the Select Lock Entries screen, fill in the Table name or use *, the

Client or use *, and the User name or use *. Click the List button.4. On the Lock Entry List screen, you can use the Refresh button to monitor the

table locks, or double-click any line for detail information. You can alsouse this transaction to delete a table lock or all table locks, ifnecessary.

5. You may now leave the SM12 transaction.

Return to Index...

Viewing Update Lock Information

Occasionally, due to a dropped user session or some other unknownreason, an update transaction fails. When this happens, locksplaced on resources may not be released. If an object was markedas currently being updated, and the update fails, the lock may

still be present in the SAP system. Any other transactionsattempting an update on the locked object fail. Database errors,including SAPSQL_ARRAY_INSERT_DUPREC errors, appear in the systemlog. To remove these update locks, you should try to force theupdate to complete. If the update cannot be forced to completion,the lock should be removed from the object.

1. Log on to any client in the appropriate SAP system.2. Go to transaction SM13.3. On the Update Records: Main Menu screen, if you are looking for the update

locks produced by a specific user and\or in a specific client, type in the


26/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Client and\or User. Using a From date and To date range can help as well.But if the originating lock happened some time ago, using a date range willnot help. Normally, there arent that many hanging update locks at onetime, so dont worry about being too specific. When you have entered allyour information, press Enter.

4. The Update Records screen contains a list of outstanding update recordsmatching your selection criteria. If the list is empty, go back to theprevious screen and open your search by using * in client and user, and adate range of 01-01-2000 through 12-31-2010. If you still get no results,there are no incomplete update records.

5. The best way to resolve incomplete update records is to try to force them tocompletion. From the top-most menu of the Update Records screen, clickUpdate records Update All records.

6. You will see an Update Updating update requests which have not yetexecutedpopup. If, after reading this information message, you decide thatdeleting the update records would be a wiser decision, skip to step 7.Otherwise, click the green picture-icon. You will be given one lastchance to stop via a Update selected records popup. Click Yes to start theupdate.

7. If the update records are fairly old (a day or so) and\or the update forceproduces an error, or you are unsure whether forcing the update record tocompletion is the wisest choice, forcing the update may not be an option.If this is the case, deleting the update lock is probably your best courseof action. From the top-most menu of the Update Records screen, clickUpdate records Delete All records. You will be given an opportunity tochange your selection criteria in the Delete Update Records popup. Clickthe green picture-icon to continue. You will be given one last chance tostop via a Delete data will be lost popup. Click Yes to start the delete.

8. You will not receive a confirmation message after the update or delete. Youmay now leave the SM13 transaction.

Return to Index...

Viewing OS Server Files from SAP

The SAP directory structure on a Windows server can be viewed via SAP using theAL11 transaction. All the usual SAP directories are accessible as well as anycustom data views. Text files can be accessed and ported in and out of the SAPinstance. Directories can be sorted by Name or Date\Timestamp.

Return to Index...

Transport Tasks

Configuring TMS - Transport Management System - for the First Time

Note: if you already have a TMS configured, do not use this section to add a newinstance to the existing TMS configuration. You could severely damage any pre-existing transports, making them untransportable. Instead, use the followingsection Adding New Instance to TMS Setup.

1. Log on to client 000 of the SAP instance to serve as the Domain Controller.2. Go to transaction SE06.3. Click on the Perform Post Installation Actions button.4. Go to transaction STMS.5. You should see a popup box with the title TMS: Configure Transport

Domain. If the popup doesn't say that, press F6 to change to thecorrect popup box.


27/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.6. Fill in the TMS: Configure Transport Domain popup with the

Description, Name of DOMAIN_, and the description of theTransport Domain. Then click Save.

7. On the Transport Management System screen (if you arent there, back out untilyou are), assuming that this is the first SAP instance and there are no otherinstalled SAP instances in your landscape yet, and assuming that youwant your transport requests to be transportable and not local only,click on Overview Systems.

8.On the System Overview Domain Domain_screen, click SAP System Create External System. Fill in QAS if you are going to have a three systemconfiguration or PRD if you are going to have a two system configuration, ormake up a if you are never really going to have another SAP system. Fillin the rest of the information including the Path which is assumed to be\\:\usr\sap\trans for NT or \usr\sap\trans for UNIX. ClickEnvironment Transport Routes.

9. On the Display Transport Routes screen, click the User Settings button, turnon the Hiergraphical List Editor, and click the Continue button. Back outof the screen and then go back in you should see the list in a text modewhich makes it easier to handle.

10. On the Display Transport Routes screen, click the DisplayChange button totoggle into Change Mode.

11. On the Change Transport Routes screen, click Configuration StandardConfiguration Development and Production System.

12. Fill in the Development and Production System popup, using your current SAPsystem SID as the Development system and the SAP instance you created in step#8 as the Production system. Click the mark to Continue.

13. Back on the Change Transport Routes screen, click the Save icon and confirmall the popup questions.

14. On the Change Transport Routes screen, back out until you can once more seethe Transport Management System screen. Click Overview Systems.

15. On the Display TMS Configuration: System XXXscreen, double-click the TMSDomain domain controller SAP instance.

16. On the Display TMS Configuration: System XXXscreen, click the DisplayChangebutton to toggle into Change Mode. Click the Communication tab and make surethat the Transport Group Name is correct. It should contain of the DomainController in the format of DOMAIN_ where is the System ID of theSAP Domain controller. Use the dropdown to find the correct entry it thefield is blank. Click the Transport Tool tab. Verify that the information onthe tab is correct and click the Insert Rowbutton. Add a Parameterof CTCand a Value of 1. Click the Save button.

17. Do step #16 for every system in your TMS Domain, making sure to change allTransport Group Names are the same and the CTC row is added to each with avalue of 1.

18. Save your way back the the main STMS screen.19. You may now leave STMS.

Return to Index...

Adding a New SAP Instance to an Existing TMS Domain Controller

1. Log on to client 000 in the SAP instance you want to add to the existing TMSDomain.

2. Go to transaction SE06.3. Click on the Perform Post Installation Actions button.4. Go to transaction STMS.5. You should see a popup box with the title TMS: Configure Transport

Domain. Press F6 until you see a TMS: Include System inTransport Domain popup.


28/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.6. Fill in the TMS: Include System in Transport Domain popup with the

Description, Target Host, and System numberof the TMS DomainController then click Save.

7. You should see a message that says SAP System waiting to beincluded in the Transport Domain.

8. Log on to client 000 of the Transport Domain Controller and go to transactionSTMS, keeping your original session in the other SAP instance open.

9. On the Transport Management System screen, click Overview Systems.

Highlight the System you just added and then click SAP System Approve.Then confirm all the messages.10. Back on the Transport Management System screen, click Environment

Transport Routes.11. On the Display Transport Routes screen, click the DisplayChange button to toggle into Change Mode. Click on Edit Transport Route Create.11. On the Create Transport Route popup, use the Consolidation boxes to enter

the SID of the transport domain, create a Z* transport layer, and the SIDof the system you are adding. Click Save and confirm. Back out to the main

Transport Management Screen.12. Back on the Transport Management System screen, click Overview Systems.

Double-click on the new system, and click on the Communications tab. Makesure that the Transport Group name is the name of the original transport

domain. If not, change it. Click the Transport Tool tab. Verify that theinformation on the tab is correct and click the Insert Rowbutton. Add aParameterof CTC and a Value of 1. Click the Save button.

13. You can switch back to the new instance, and confirm that the SAP Systemwaiting to be included in the Transport Domain has disappeard.

14. You may now log out of both SAP instances.

Return to Index...

Make a Local Transport into a Transportable Transport

Sometimes, mistakes just happen. For this example, we will use a transportSM1K00047 as the erroneous change request. Make sure to release SM1K00047 beforebeginning this procedure.

1. Log on to the client who is the owner of the local transports that needsfixed.

2. Go to SE03.3. On the Transport Organizer List screen, click on Merge Object Lists which is

in the Requests\Tasks section.3. On the Merge Objects List screen, put SM1K00046 in the first Request\Task

field. Make sure that the Releasedcheck box is "on" in the Request Statussection and click the Execute icon.

4. On the Merge Objects List screen, click on the Merge icon.5. On the Enter Transport Request popup, click the Create Request icon.6. On the Select Request Type popup, click "on" radio buttion Workbench Request.

7. On the Create Request popup, fill in the necessary information and make surethat the fill in the Target field so that the transport request is NOT local.Click the Save, OK, icon, etc. until everything is done. You willget a new transport request number, in our case SM1K00050. This new requestcan be released using one of the transport organizer Transactions like SE10,etc. Once it is released, you can go to \usr\sap\trans on the OS level and indirectory cofiles copy K00050.SM1 to K00046.SM1, and in directory data copyR00050.SM1 to R00046.SM1.

8. You may now leave SE03.


29/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Once you have control of your session again, the transports are done. Verifytheir return code in the Import Queue list. It shoud have been updatedautomatically.

Return to Index...

Transporting Change Requests

To manually transport change requests from DEV\QAS to PRD:

1. Make sure the change request(s) has been released via Se10 or one of the otherTransport Organizer Transactions.

2. Go to transaction STMS and click Overview Imports. Double-click the PRDqueue.

3. Click the refresh button to make sure you have the most current view of thePRD queue. Make sure the change request(s) you want to transport shows in thequeue.

4. Using the F9 button, highlight all the transactions you want to manuallytransport.

5. Click on Extras Activate Inactive Requests. Confirm the popup. Thisbypasses the STMS_QA process.

6. Leave the change requests highlighted. Click Request Import. On the popup,make sure that the target is client 300. Make sure that Synchronous radiobutton is "on" in the Execution tab. Make sure that the first three optionsare checked "on" in the Options tab. When you are done, click on the green and confirm the next popup.

Once you have control of your session again, the transports are done. Verifytheir return code in the Import Queue list. It shoud have been updatedautomatically.

Return to Index...

Adding a Change Request to a Transport Queue

1. Make sure the change request(s) has been released via Se10 or one of the otherTransport Organizer Transactions.

2. Go to transaction STMS and click Overview Imports. Double-click the PRDqueue.

3. Click on Extras Other Requests Add. Fill in the Number of the TransportRequest to be added to the queue and then press Enter.

4. Confirm the Add Transport Request popup. The transport request should nowappear at the bottom of the queue list.

Return to Index...

Viewing the Transport Queue History

1. Go to transaction STMS and click Overview Imports. Double-click the queuefor which you want to view the history.

2. Click on the Import History button or press Ctrl+F7. The resulting list canbe sorted and filtered to produce a more exacting report if needed.

Return to Index...

Re-Transport Several Change Requests at Once


30/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.1. Go to transaction STMS and click Overview Imports. Highlight the queue into

which the transport(s) to be moved again were originally transported theFROM queue - and click the Import History button or press Ctrl+F7.

2. If your SAP instance is older, you may have a very long Import History list inthe next screen. Use some of the available filters and sort options to createa more controllable list of transports. Use the F9 to select and\or unselectas many as you need to transport.

3. Once all choices have been made, click Request Forward System. Fill inthe TO system and click on the Execute green mark.

4. Now you can go to the TO queue and refresh the list. Your imports shouldall be there.

Return to Index...

Transport Tool System Confirmation

1. Go to transaction STMS and click Overview Imports.2. On the Import Overview screen, click Import Queue Check Transport Tool.

You may get a message asking if you want to check the the transport tool forall systems. If only want to check a limited subset of the SAP instances, useF9 to select and\or deselect those systems before you click Transport Tool.

3. On the TMS: Check Transport Tool screen, a list of all selected SAP instancesto be checked will appear.If you see any thing but red green Oks, expand all the lines with the non-OKmarks and look for more information. Correct these problems and then run thisreport again until it comes back clean.

Return to Index...

Use Target Groups to Transport to Mulitple Clients in Two Different Instances

1. Log on to client 000 of your TMS Domain Controller SAP Instance.2. Go to transaction STMS.

3. On the Transport System Management screen, click Overview TransportRoutes.

4. On the Display Transport Routes screen, click the DisplayChange button totoggle into Change mode. Click on the Target Groups line and click theCreate button.

5. In the Create Transport Group popup, fill in the Target Group as \XXXCLNTS\,give a Short Description and click the Client Assignment button. Be awarethat the Target Group name must start and end with a \.

6. Enter each Target system and Target client you need. For our example, we willDEV 100, QAS 200, and QAS 210. Click the green check mark to Transfer. Younow have a target group. Now you must create a Consolidation Layer.

7. Back on the Change Transport Routes screen, click on Transport Routes andclick Create.

8. In the Create Transport Route popup, click the Extended Transport Controlbutton at the bottom of the popup. Make sure Consolidation is "on" and fillin the information using our Target Group as the Consolidation Target.9. Click the green check button to Save the change.10. You now have a Transport Group. Confirm the Disturbution of it to the other

SAP Instances.

Return to Index...

Configure TMS to Use SAP's Quality Assurance Functionality

A Quality Assurance system must have a) a delivery route leading from it toanother instance, and b) be the target of a consolidation route. See topic


31/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Using Target Groups to Transport to Mulitple Clients in Two Different Instancesto fulfill the a) requirement.

1. Log on to client 000 of your TMS Domain Controller SAP Instance.2. Go to transaction STMS.3. On the Transport System Management screen, click Overview Transport

Routes.4. On the Display Transport Routes screen, click DisplayChange button to

toggle into change mode. Click on the instance in which you want to controlQA. Normally, this is QAS and the instance to be controlled is PRD. UnderTransport Routes, click on the QAS instance and click Create.

5. On the Create Transport Route screen, make sure Deliveryis "on" and fill inSource and Delivery systems with QAS and PRD. Click the green check mark tosave. Now you have met condition a.

6. Back on the Change Transport Routes screen, click on the QAS instance andclick the single pencil Change button. You will see a Change SystemAttributes popup. Click "on" Quality Assurance - Delvery After Confirmation.If you want to change the people who OK the transports, click theProcedure button and make your changes. Then back out. Click the green checkto Transfer your changes.

7. Back on the Change Transport Routes screen, click on the Target Groups lineand click the Create button.

8. In the Create Transport Group popup, fill in the Target Group as \XXXCLNTS\,give a Short Description and click the Client Assignment button. Be awarethat the Target Group name must start and end with a \. Enter each Targetsystem and Target client you need. Click the green check mark to Transfer.You now have a target group. Now you must create a Consolidation Layer.9. Back on the Change Transport Routes screen, click on Transport Routes andclick Create.

10. In the Create Transport Route popup, click the Extended Transport Controlbutton at the bottom of the popup. Make sure Consolidation is "on" and fillin the information using our Target Group as the Consolidation Target. Clickthe green check button to Save the change.11. You now have a Transport Group. Confirm the Disturbution of it to the other

SAP Instances.

12. You may now leave the STMS transactions.

Return to Index...

Automate the Transport Process

1. Log on to client 000 of your TMS Domain Controller SAP Instance.2. Go to transaction STMS.3. On the Transport System Management screen, click Overview Imports.

Double-click on the queue for the SAP instance are in.4. On the Import Queue screen, click the Refresh button. Click on the Import

All Requests button.5. On the Start Import popup, fill in the information for the job. Make sure "At

Start Time" is on. Although Period appears grayed out, you can still changeit to the periodic value you need. I recommend every hour in DEV, 4 times aday in QAS, and once an evening in PRD. Click on the green check mark toContinue.

6. You may now leave the STMS transaction. If you ever need to change this job,you must do it via STMS and not SE37.

Return to Index...

User Tasks


32/66

This documentation is the intellectual property of Jo Spencer and may not be edited without permission.Creating, Modifying, and Deleting Users

Creating a User

1. Log on to the appropriate SAP system and the client where the new user is tobe added.

2. Go to transaction SU01.3. On the User Maintenance: Initial Screen screen, type in the new User name

and click the blank page picture-icon.4. On the Maintain Userscreen, fill in at least the following information foreach tab:

Address Last name, First name, Internet mailLogon data Initial password, repeat password, user typeDefaults Decimal formation, Date formation, Time zone,

OutputDeviceRoles Select roles to be added to the userProfiles Selectprofiles to be added to the user

When all necessary data has been entered, click the Savepicture-icon.

5. You will receive a User savedmessage in the status bar at the bottom of thescreen. You may now leave the SU01 transaction.

Return to Index...

Copy an Existing User to a New User

1. Log on to the appropriate SAP system and the client where the user is to bechanged.

2. Go to transaction SU01.3. On the User Maintenance: Initial Screen screen, type in the User name to be

copied and click the double blank page picture-icon.4. On the Copy Userpopup, type in the To for the new user and click the Copy

button.5. On the Maintain Userscreen, click on the tabs and make the changes to the

users information. When you are done, click the Save picture-icon. Youwill receive a User savedmessage in the status bar at the bottom of thescreen.

6. You may now leave the SU01 transaction.

Return to Index...

Modifying a User

7. Log on to the appropriate SAP system and the client where the user is to be

changed.8. Go to transaction SU01.9. On the User Maintenance: Initial Screen screen, type in the users name and

click the pencil picture-icon.10. On the Maintain Userscreen, click on the tabs and make your user

information changes. When you are done, click the Save picture-icon.11. You will receive a User savedmessage in the status bar at the bottom of the

screen. You may now leave the SU01 transaction.

Return to Index...

7/28/2019 BasisOpera

BasisOperations Windows

Documents