90959 basis operations unix linux

8/6/2019 90959 Basis Operations UNIX Linux

1/65

.

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?


2/65

.

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


3/65

.

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


4/65

.

....request a new License Key?

....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/65

.

System Tasks

Starting the SAP Instance

The normal SAP instance start up consists of three parts: starting the SAP OS Collector, startingthe Oracle Listener, and starting the SAP instance. The process mainly goes like this: oralogs on and starts the Oracle Listener then adm logs on and runs the startsap script.

What? You say we missed a step? What happened to the SAP OS Collector?

The startsap script takes care of the SAP OS Collector for us. When the SAP Instance starts upvia the startsap script, it checks to see if saposcol is up and running whether from the root userstarting it manually or from another SAP Instance already starting it up, it doesnt matter. Ifsaposcol is up and running, the script simply moves on to the next step. If it is not, the scriptstarts saposcol as root and then proceeds. So the SAP OS Collector gets handled one way oranother.

Even if you have multiple SAP instances on a server, the process is pretty much the same unlessthe Oracle databases were installed using the MCOD installation option. Then only one OracleListener is used since both databases share one Oracle listening port which is normally 1527.Normally each SAP database ie SAP instance - has its own listener.

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

1. Verify that the SAP instance is down.

2. Log on to the appropriate server as ora.3. Type in the following:

lsnrctl start

4. Log on to the same server as adm.

5. Type in the following the saposcol will come up automatically:

startsap

If you only need to start the database and not the SAP instance too, typeinstead:

startsap DB

And do not do the rest of the start up procedures listed below, you can stop now.6. Wait until the startup messages have scrolled by. There may be other minor programs

that start at the time as well. If you try to logon and are refused connection, check thelogs in the /home/adm for applicable errors.

Return to Index...

Verifying that the SAP Instance is up

The easiest way to confirm that the SAP instance has started successfully is to log on to theinstance. If it has not had a successful start up, look at the logs in the /home/admdirectory. Sort them witj ls ltr is see the list sorted in descending order for the ease ofviewing.

If nothing obvious is found, go to the /usr/sap//DVEBMGS00/work directory and do thesame thing in this directory. The most useful information can be found in the dev_wx, dev_ms,dev_disp, dev_rfcx, and stderrx files.


6/65

.

If you need further assistance, please refer to the section SAP System Start Up Troubleshooting.

Return to Index...

Stopping the SAP Instance

The stopping of a SAP instance is practically the reversal of the start up

Process; stop the SAP instance, stop the Oracle Listener, and stop the SAP OSCollector. The only real difference is that the stopsap script will NOT stop the SAP OS Collectorfor you, you have to stop that manually once everything else it down. There could be other SAPinstances still running so the OS Collector needs to continue to gather information.

1. Log on to the appropriate server as adm.

2. Type in the following:

stopsap

If you only need to stop the SAP instance and not the database too, typeinstead:

stopsap R3

And do not do the rest of the start up procedures listed below, you can stop now.3. Log on to the same server as ora.4. Type in the following:

lsnrctl stop

5. Log on to the same server as root.6. Type in the following:

cd /usr/sap//SYS/exe/run./saposcol -k

7. Log off the server.

Return to Index...

Starting the SAP OS Collector

1. Log on to the appropriate server as adm.2. Type in the following:

cd /usr/sap//SYS/exe/run./saposcol


Return to Index...

Stopping the SAP OS Collector

1. Log on to the appropriate server as adm.2. Type in the following:

cd /usr/sap//SYS/exe/run


7/65

.

./saposcol -k


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 those companys whodo not yet possess a solid backup and recovery solution, or who simply want to segragate theSAP 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 makebased on their history with similar procedures at your company, the recommendations of SAP,and the guidance of your implementation Basis consultant. Enforced backups, and detailed andtested recovery procedures should be part of any Disaster Recovery plan, and a documentedpart of any SAP implementation project.

If your company falls into the latter category, SAP does supply tools for your uses which can beused in either line command form or from within the SAP instance. If you SAP server contains atape drive or has access to the network tape unit, transaction DB13 can be used to scheduleperiodic backups. This is the same transaction where weekly statistics, log cleanup, anddatabase verification jobs are scheduled in the post-installation work after installation of a newSAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed in command lineform by the IT staff.

For more information, please see the SAP Online Documentation for DB13 by going to the DB13transaction and clicking Help -> Application Help or referring to the section Creating DatabaseStatistics, Index Rebuilds, and Log Backup Jobs Oracle.More information regardingBRCONNECT can be found in the SAP BRCONNECT Guide which can be found athttp://service.sap.com/instguides.

Return to Index...

What Needs to Be Backed Up?

The PRD Instance

Daily backup should be made for these SAP specific directories:

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

Daily backups should be made for these Oracle specific directories:

/oracleDirectory holding redo logs if not in the /oracle structure

Weekly backup should be made for these OS specific directories:

Root/etc/dev
http://service.sap.com/instguideshttp://service.sap.com/instguides


8/65

.

For Oracle, the entire /oracle directory should be backed up daily if there is only one OracleInstance on the server, and each separate /oracle/ directory if there is more than oneinstance on the server.

It is also recommended that a full offline image of the entire server be made before the monthlyclosing cycle.

The DEV and QAS Instances

Weekly backup should be made for these SAP specific directories:

/usr/sap//sapmnt/Any directories containing flat files that are used by the SAP instance

Weekly backups should be made for these Oracle specific directories:

/oracleDirectory holding redo logs if not in the /oracle structure

Monthly backup should be made for these OS specific directories:

Root/etc/dev

For Oracle, the entire /oracle directory should be backed up daily if there is only one OracleInstance on the server, and each separate /oracle/ directory if there is more than oneinstance on the server.

It is also recommended that a full offline image of the entire server be made at the same timeevery month.

Return to Index...

Working with saprouter

Starting saprouter (OSS Link)


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 with SAP viasaprouter in the past, there can only be three reasons for a broken SAPNet connection to SAP:the SAP VPN is down (which rarely happens); your saprouter configuration has been incorrectlychanged (also very rare); or your saprouter is not running (happens all the time).




9/65

.

3. Look at the SAPROUTER service. If is not started, right-click to start the service. If it isstarted, right-click & Stop the service and then right-click & Start the service. This shouldbounce your saprouter instance.

4. You may now log off the server.

Return to Index...

Stopping saprouter



3. Right-click on the SAPROUTER service and click Stop.4. You may now log off the server.

Return to Index...

Applying a SAP Note

Not all SAP Notes can be applied via the SNOTE transaction. Some are information only,

providing no code corrections. Others entail corrections that can only be done manually. Thislatter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAPprogrammer. Also, SAP recommends that SNOTE change requests NOT be transported into othersystems. Use the SNOTE transaction in each SAP system that needs the correction, and deletethe generated change requests since they should never be transported and could lock resourcesduring application of other SAP Notes and support package application.

If you do not have a working OSS connection, you can download an OSS note from the SAPMarketplace using the SAP Download Manager and use the upload feature in SNOTE to load itinto 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: Worklistscreen, on the top-most menu bar clickGoto SAP Note download.

4. On the Note Assistant: Download Note popup, type the number of the SAP note in the Notenumberbox and click the clock picture-icon. A SAP Note XXXXXX is being downloadedmessage will appear in the bottom status bar. If you get a communications error message,verify that saprouter is up and try again.

5. Once the SAP Note has been downloaded, it will appear on theAssistant - VersionXXX/XXXX: Worklistscreen under the SAP Notes New navigation tree. The SAP Note canonly be applied if there is a blue box with a black arrow to the left of the note number. Ifthere is a gray diamond instead, the downloaded note cannot be applied or is notapplication 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 to see if there are

any necessary manual tasks to be performed after the note is applied. When you areready to apply the note, click on the clock picture-icon.

8. If there are any prerequisite SAP Notes which need to be applied to the SAP system beforethe downloaded SAP Note can be applied, a list will appear in a Load the following notesinto your SAP system popup will appear. Click the clock picture-icon to download theseprerequisite SAP Notes as well. If any of the prerequisite SAP Notes must be applied inparallel with the original downloaded SAP Note, a list will appear in a SAP Note queue to beImportedpopup. Click the clock picture-icon to apply all the listed SAP Notes.


10/65

.

9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Note read popupwill appear. Once you have read the information contained in this popup, click the Yesbutton.

10. A standard Make repairs in foreign namespaces... popup will appear. Click the green tocontinue.

11. On the Prompt for transportable Workbench requestpopup, click the blank page picture-icon to create a new change request. On the Create Requestpopup, fill in the Shortdescription and click the Save picture-icon. You will be returned to the Prompt for

transportable Workbench requestpopup which contains the generated change requestnumber 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 NoteAssistant - Version XXX/XXXX: Worklistscreen. There is no completion message. Click thegreen and pencil picture-icon.

14. On the Set Processing Status for Note XXXXXXpopup, click on the Completedline to turnon the radio button. Click the green . You can now leave the SNOTE transaction.Modified programs, functions, etc. may require recompilation.

15. If the OSS note you applied changed a ABAP program, you must go to the SE38transaction and manually recompile the program. If it changed a function, go totransaction SE37 and click the Single Testbutton this is enough to force 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 week license. But youcant install any kind of SSCR key on a termporary instance, so it is best to get the permanentlicense key immediately.

The license key request process has been drastically overhauled by SAP over the past.Normally, if you request a new SAP license key, the information will be e-mailed to you in the

form of a script. But in case you dont receive this e-mail promptly, it is important to know howto 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. Type the following, pressing enter when you are done:

saplicense -get

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

4. You may now 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 Gethardware key.


11/65

.

4. On the Determine Remote Hardware Keypopup, find the host name or IP address for thenew SAP system server. Click the button to the left of this entry to high-bright the line.Click the Detrmne button to continue. The hardware key will appear in the box to the rightof 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 mySAPBusiness Suite.

3. On the License keys for mySAP Business Suite screen, click on the Request license keyhyperlink.

4. On the License key: Requestscreen, click the correct Installation hyperlink the mySAPBusiness Suite component.

5. On the License key request: System overview screen, click the New system button.

6. On the License key: Request for a new system screen, fill in the required information in theSystem section. In the License requestsection, fill in the Hardware keybox right abovethe Save New Item button. After you have supplied the hardware key, click the Save NewItem button. The license key request will be shifted up to the first line of the Licenserequestlist. Click on the to the left of the license request to place a in the box. Nowyou are finally ready to click the Send Requestbutton.

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 mySAPBusiness Suite.

3. On the License keys for mySAP Business Suite screen, click on the Display license keysrequested by me hyperlink.

4. On the License key: requestscreen, look for your requested key. It should appear with the you provided during the request process. If the Status shows as Sent to SAP, thelicense key has not yet been generated. If the Status shows as Completed, your newlicense key has been generated and you can click on the System hyperlink tocontinue.

5. On the License key: requestscreen, scroll down until you can see the License request

section. Under the License keyheader you will see you new SAP system license key. Writethis key down and remember that it is case sensitive. Or you can cut-and-paste it to amore convenient storage location.


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.
http://service.sap.com/licensekeyhttp://service.sap.com/licensekeyhttp://service.sap.com/licensekeyhttp://service.sap.com/licensekey


12/65


13/65

.

found in the SAP Note containing the advanced correction. Click the Registerbutton onceall information has been enter.

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


Return to Index...

Opening a Service Connection for SAP Support

Before opening a service connection for SAP, be sure that the SAPAG client has been added tothe appropriate SAP system and Client, and that a Security Audit Trace has been activated forthe SAPAG ID.

Before a Service Connection to a SAP server via your saprouter can be created, the saproutermust run the LOP Line Opener Program to initiate the mode of SAP connection. PleaseLOPInstalltion.exe on your saprouter server before trying to add and open any ServiceConnections.

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 instances line.

4. In the Enter Data for the systems semi-automatic opening popup, set the days, hours, andminutes 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 Wizardbutton.

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 ofyour SAP systems registered with SAP. From the expanded list of system, click on theradio button just left of the for which you are reporting the problem. Click theChoose button and you will be returned to the Customer messages Create screen.

5. On the Customer messages Create screen, click on the radio button to the left of the

System type which has the problem: development system, test system, orproductionsystem. From the Release dropdown, select the appropriate SAP software release. Clickthe Continue hyperlink.

6. On the next Customer messages Create screen, scroll down to the bottom of thescreen. If the problem involves an add-on, select the appropriateAdd-on andAdd-onrelease from the dropdowns; if an add-on is not involved, leave these dropdowns blank.Verify that the information showing in the Oper. System, Database, and Frontenddropdowns is correct. If it is not correct, selection your SAP systems information fromthe appropriate dropdowns. Click the Continue hyperlink.

7. On the next Customer messages Create screen, scroll down to the bottom of thescreen. From the Prioritydropdown, select the appropriate priority ofLow, Medium,High, or Very High. From the Componentdropdown, select which SAP component is
http://service.sap.com/serviceconnectionhttp://service.sap.com/messagehttp://service.sap.com/messagehttp://service.sap.com/serviceconnectionhttp://service.sap.com/message


14/65

.

having the problem. Once you select a component, a secondary Component dropdownwill appear. Select a secondary component and a third component as well. Do the bestyou can to make all three component pieces fit your problem as closely as possible.Click the Continue hyperlink.

8. On the next Customer messages Create screen, scroll down to the bottom of thescreen. Select a language from the Language dropdown, type a short but descriptivesummary of your problem in the Short description box, and type a more detaileddescription of your problem in the Long testbox.

9. If there are logs or other files which might assist SAP in resolving the issue, rename themall so that they have a suffix of .log and use theAdd attachmenthyperlink and the

Attachments popup to attach them to the message. After attaching all the necessaryfiles, click the Close hyperlink to return to the Customer messages Create screen.

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

11. You will receive a confirmation screen with a generation problem number. Write thisproblem 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 theOutput devices button.

4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon toswitch into change mode. The easiest way to create a new printer is to copy an existingone. Click on a similar printer in the output devices screen then click the create withtemplate picture-icon.

5. On the Spool Administration: Create Output Device screen, fill in the Output device andShort name. Make any changes that are unique for the new printer on the Device

Attributes and Host Spool Acc Methodtabs. When all the required data has beenchanged/added, click the Save picture-icon.

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

7. You may now leave the SPAD transaction.

Return to Index...

Modifying a Print Device

http://service.sap.com/messagehttp://service.sap.com/message


15/65

.



4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon toswitch into change mode. Double click on the output device to be changed.

5. On the Spool Administration: Output Device (Change) screen, make any necessarychanges on the Device Attributes and Host Spool Acc Methodtabs. When all the requireddata has been changed/added, click the Save picture-icon.

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


Return to Index...

Deleting a Print Device



3. On the Spool Administration: Initial Screen screen,under the Devices/servers tab click the

Output devices button.4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to

switch into change mode. Click on the output device to be deleted and then click the trashcan picture-icon.

5. On the Spool admin.: Delete screen, verify that the correct printer is about to be deleted.Click the Yes button.

6. You will receive an Output device deletedmessage in the status bar at the bottom of thescreen. You may now leave the SPAD transaction.

Return to Index...

Transporting a Printer or a Group of Printers




4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon toswitch into change mode.

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

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

7. On the Prompt for Workbench requestpopup, click the blank page picture-icon to create anew change request. On the Create Requestpopup, fill in the Short description and clickthe Save picture-icon. You will be returned to the Prompt for transportable Workbenchrequestpopup which contains the generated change request number for this systemchange. Click the green to continue.

8. You will receive an Entry is made in transport requestmessage in the status bar at thebottom of the screen. Repeat steps 11 through 14 as many times as necessary, using thesame transport request for all printers.


Return to Index...


16/65

.

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.




4. On the Spool Administration: List of Output Devices screen, double click on the printer youneed 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 theAdministration: Output Device (Change) screen, on the top-most menu bar clickEdit Reactivate.

7. On the sameAdministration: Output Device (Display) screen, on the top-most menu barclick Edit Reset Cache.

8. On the sameAdministration: Output Device (Display) screen, on the top-most menu barclick Edit NI Reset.


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 very easy tounderstand. As a rule, local printer is simply another way of saying that the user is going toprint to the default printer designated on his/her workstation. You probably do this all the timewith Windows to printer spreadsheets, Word documents, etc without thinking about it. You can

do the same thing using SAP.

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


17/65

.

Using this printer will cause print to go to SAPLPD which will use the default printer of the currentworkstation.

Return to Index...

Viewing a List of Pending Printer Output Requests for All Printers

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

2. Go to transaction SP01.

3. On the Output Controller: Spool request selection Screen screen,click on the Outputrequests tab.

4. On the Output Controller: Output request selection Screen screen, fill in any informationneeded to filter the selection results. Then click on the clock picture-icon.

5. A list of all pending output requests will be displayed.

6. You may now leave the SP01 transaction.

Return to Index...

Viewing a List of Output Requests for a Specific Printer



3. On the Spool Administration: Initial Screen screen,under the Devices/servers tab click theOutput devices button. On the Spool Administration: List of Output Devices screen, clickon the printer where you need to check the output requests. Then click on the printer andpage picture-icon.

4. A list of all pending output requests for the selected printer will be displayed.


Return to Index...

Reprinting a Document



3. On the Output Controller: Spool request selection Screen screen,fill in any informationneeded to filter the selection results. Then click on the clock picture-icon.

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

5. Click on the printer picture-icon. An Output request createdmessage should appear in thebottom status bar.


Return to Index...

Re-routing Print to a Different Printer



3. On the Output Controller: Spool request selection Screen screen,fill in any informationneeded to filter the selection results. Then click on the clock picture-icon.

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


18/65

.

5. Click on the printer with a box outline picture-icon. On the Output controller: Print spoolrequest XXXXscreen, tab down to the line reading Output device and select a new printer.Click on the printer picture-icon.

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

7. On the Confirm redirection of outputpopup, click the Yes button. An Output requestcreatedmessage should appear in the bottom status bar.


Return to Index...

Deleting Obsolete Temporary Objects and Reclaiming the Space



3. On the TemSe --- Administration of Temporary Sequential Data screen, on the top-mostmenu bar click TemSe database Reorganization.

4. On the TemSe --- Administration of Temporary Sequential Data popup, click theAll TemSeobjects older than option to turn on the radio button to the left. Fill in the Days box with7 for development and quality assurances SAP systems, and 32 in production SAP

systems. Click the Delete button.5. On the TemSe objects older than XX days popup, click the Yes button.

6. After the successful deletion of the selected temporary objects, you will be returned to theTemSe --- Administration of Temporary Sequential Data screen. There is no taskcompletion message.


Return to Index...

Mass Recompilation of ABAP Programs


2. Go to transaction SGEN.

3. On the SAP Load Generatorscreen - Generation tasksection, click on the line readingGenerate all objects in selected software components to turn on the radio button to theleft. Click on the Continue button at the bottom.

4. On the SAP Load Generatorscreen - Selection by software components of generation setsection, click the button to the left of each entry listed in the Software componentbox.Click the Continue button at the bottom of the screen.

5. On the SAP Load Generatorscreen Select server for parallel generation section, thereshould only be one entry in the Serverbox. Click the button to the left of this entry. Clickthe Continue button at the bottom of the screen. Several messages will appear in thebottom status bar before the next screen appears.

6. On the SAP Load Generator Job Monitorscreen, fill in the time and date listed under the

Schedule job atbutton located at the bottom of the screen. Click on the Schedule job atbutton.

7. On the SAP Load Generator Job Monitorscreen Load generator status section, the statusof mass generation is shown. You may now leave the SGEN transaction and later return tocheck the progress of the recompilation. No other load regeneration jobs can be scheduleduntil this one completes. If a load regeneration jobs fails for some reason, return to theSGEN screen for instructions on how to restart the job.

Return to Index...

SAP IGS Server


19/65

.

The IGS server (Internet Graphics Server) component displays and generates the graphics usedby SAPGui HTML users. For example, the BW users accessing reports via the internet use theIGS server. The ITS server also channels graphics through the IGS server. The IGS server isinstalled as a started service on each server.

Starting the IGS instance

1. Log on to the appropriate server as adm.2. Type the following:

cd /usr/sap//DVEBMGS00/igs./bin/startigs -p .

3. You may log off the server.

Stopping the IGS instance

4. Log on to the appropriate server as adm.5. Type the following:

cd /usr/sap//DVEBMGS00/igs./bin/stopigs

6. You may log off the server.

Return to Index...

Support Tasks in the SAP 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 betweennormal lag time, and the possibility of something being wrong.

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

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

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

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

4. On the User Data Maintenance screen, fill in the gathered information from step #1. Thenpress Save. You may or may not receive a confirmation message.

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
http://service.sap.com/user-adminhttp://service.sap.com/user-admin


20/65

.


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

3. On the User Data Maintenance screen, you will see a list of your mostly recently generatedOSS IDs. If the user ID you are seeking does not appear on the screen, you can fill in anyof the information allowed in the top row to performa a search.

4. Verify the status of the OSS ID for which you are looking. If the Status reads Successful,and both the User ID and Initial Passwordfields contain legitmate data, your OSS ID hasbeen generated and you can pass the information on to your user.If the Status reads Requesting, your OSS ID has not been generated so come againlater to check the status. If the Status makes reference to some type of error condition,please open an OSS problem to get it resolved. The normal turnaround for an OSS IDgeneration 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 and maintain users.You may be asked for your OSS ID and password again, dependently on your point oforiginal logon.

3. On the User Data Maintenance screen, click Search for an entire list of your SAP

Marketplace users, or fill in the provided fields to help narrow your search, pressing Searchwhen you are ready.

4. From the second User Data Maintenance screen, click on the Surname of any user you wishto change.

5. On the next User Data Maintenance screen, click on theAuthorizations tab, and then clickthe Editbutton on the bottom of the displayed section.

6. From the resulting User Data Maintenance Authorization objects overview screen, click ona line you want to change. For example, if you want the OSS ID to be able to create newOSS problems with SAP, click the Create Customer messages on box at the far left to theline.

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

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

9. When all the changes have been completed, make sure you are at the same screen as instep #6 and click Save. You should get a screen thanking you and saying that yourchanges have been saved.


Return to Index...

Creating, Modifying, and Deleting System Parameters
http://service.sap.com/user-adminhttp://service.sap.com/user-adminhttp://service.sap.com/user-adminhttp://service.sap.com/user-admin


21/65

.

Creating System Parameters


7. Go to transaction RZ10.

8. On the Edit Profiles screen, select the _DVEBMGS00_SAP Profile from thedropdown, or whatever instance profile you need to change. In the Edit profile section,click the radio button to the left ofExtended maintenance. Click the Change button.

9. On the Maintain R/3 Profile screen, click theAdd Parameterbutton.10. 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 green picture-icon twice.

11. On the Maintain R/3 Profile popup, click the Yes button to save your changes.

12. On the Edit Profiles screen, click the Save picture-icon.

13. On the Save profile popup, click the No button.

14. On theActivate profile popup, click the Yes button.

15. On the Edit Profiles popup, click the green button.

16. On the Caution! Caution! Caution! popup, click the green button.17. 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.

18.You will not get a confirmation message. You may now leave the RZ10 transaction.

Return to Index...

Modifying System Parameters




4. On the Maintain R/3 Profile screen, locate the parameter that needs to be changed in the

Parameter name column. Change the matching value under Parameter value to the newvalue. Click the Copybutton. Click the white arrow on green picture-icon.







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

Return to Index...

Deleting System Parameters





22/65

.

4. On the Maintain R/3 Profile screen, locate the parameter you need to delete and click onthe Parameter name to high-bright it. On the top-most menu bar, click ParameterDelete.

5. On the next Maintain R/3 Profile popup, make sure that the parameter listed is the one youneed to delete. Click the Yes button to delete the parameter. You will receive a Parameterwas deletedmessage in the status bar at the bottom of the screen. Click the Copybutton.Click the white arrow on green picture-icon.







12. You may now leave the RZ10 transaction.

Return to Index...

Overview of All Work Processes Running on a SAP System


2. Go to transaction SM50.

3. On the Process Overview screen, all processing threads for the SAP system are displayed.If a thread is being used, the name of the report running will be displayed as well as thenumber of seconds that the report has been running, the client in which the report isrunning, the action the report is currently doing, and, if applicable, the table the report iscurrently accessing.

4. Click on the blue arrow circle picture-icon to refresh the process data appearing on thescreen.

5. Click the white clock picture-icon to display the amount of CPU time consumed by eachprocess thread so far.

6. Double click any display line containing a report name in order to see more detailedinformation about the running report. This information includes database access statisticsand timings. Use the white arrow on green picture-icon to go back to the ProcessOverview screen.

7. Click on any process thread and then click the blue cylinder with glasses picture-icon. Thiswill display the Trace Data screen which shows the actual communication between SAP,the operating system, and the database server. This information is useful when trackingprocess thread problems. Use the white arrow on green picture-icon to go back to theProcess Overview screen.

8. You may now leave the SM50 transaction.

Return to Index...

Stopping Run-Away or Bad Work Processes



3. On the Process Overview screen, find the process which must bestopped. 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 ProcessOverview screen until the stopped process has cleared from thedisplay.


23/65

.


If this does not kill the process, you can go to transaction SM04 and kill the users session. If thisdoes not kill the process, you can log on to the server, open a Task Manager session, and Endthe Process. If this does not kill the session, there is an executable in the RUN directory on theserver called sapntkill.exe. Run it providing the process ID number. If none of the above work,you have no choice but to bounce the SAP instance and/or possibly the serve.

Return to Index...

Increasing or Decreasing the Number of Work Processes





5. On the Maintain R/3 Profile screen, locate the dialog processes rdisp/wp_no_dia line in theParameter name column. Change the matching value under Parameter value to the newvalue. Click the Copybutton. Do the same for the batch processes, rdisp/wp_no_btc, andthe update processes, rdisp/wp_no_vb. Be sure to click the Copybutton after each change.When all the changes have been made, click the white arrow on green picture-icon.





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



3. On the System Messages screen, click the Create button.

4. On the Create System Messages popup, type up to 3 lines ofSystem message text. Selecta server (there should only be one) from the Serverdropdown. If you want to limit the

message to one client, select a client from the Clientdropdown. If desired, fill in an Expirydate and/or Delete date. Click the green to save the message.

5. A System message addedmessage will appear in the bottom status bar. You may nowleave the SM02 transaction.

Return to Index...

Modifying a System Message



24/65

.


3. On the System Messages screen, double click on the Idnumber of the message that needsto be changed.

4. On the Display System Messages popup, click the pencil and glasses picture-icon to switchto change mode.

5. On the Change System Messages popup, make your changes and click the green to savethe changed message.

6.A System message changedmessage will appear in the bottom status bar. You may nowleave the SM02 transaction.

Return to Index...

Deleting a System Message



3. On the System Messages screen, click on the Idnumber of the message to highlight themessage 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 nowleave the SM02 transaction.

Return to Index...

Sending a System Message to a Single User


2. Go to transaction SE37.

3. On the Function Builder: Initial Screen screen, type in the Function name TH_POPUP.Click the Single Testwrench 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 sent to the specified user.

5. You may now leave the SE37 transaction.

Return to Index...

Locking R/3 Transactions



3. On the Transaction Code: Lock/Unlockscreen, you will see an empty box at the very

bottom of the screen. Type in the transaction code you want to lock and press Enter.4. The transaction code to be locked should appear at the top of the transaction list. Place a

in the to the left of the transaction to be locked by pressing Space. Press Enter.

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

Return to Index...

Short Dump Analysis


25/65

.

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 its error routines.While it is not a function of the Basis support team to debug SAP programs, familiarity withsome of the dump sections can be valuable for SAP Note searches and/or logging systemproblems with SAP.


2. Go to transaction ST22.

3. On theABAP runtime errors screen, you can click the Todaybutton for todays dumps, theYesterdaybutton for yesterdays dumps, or use the Own Selection section of the screen tonarrow down your time date/time range and then click the Start you selection button.

4. On the List of Selected Runtime Errors screen, double-click on any short dump you want toexamine more closely.

5. On the Runtime Error Long List screen, make note of the error that occurred in the WhatHappened? section, any unique information in the Error analysis section, and search termsfor searching SAP Notes in the How to correct the errorsection.

6. You may now leave the ST22 transaction.

Return to Index...

Viewing Database Lock Information


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



3. On the Select Lock Entries screen, fill in the Table name or use *, the Clientor use *, andthe User name or use *. Click the Listbutton.

4. On the Lock Entry Listscreen, you can use the Refresh button to monitor the table locks, ordouble-click any line for detail information. You can also use this transaction to delete atable lock or all table locks, if necessary.


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 maystill 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,


26/65

.

the lock should be removed from the object.



3. On the Update Records: Main Menu screen, if you are looking for the update locksproduced by a specific user and/or in a specific client, type in the Clientand/or User. Usinga From date and To date range can help as well. But if the originating lock happened some

time ago, using a date range will not help. Normally, there arent that many hangingupdate locks at one time, so dont worry about being too specific. When you have enteredall your information, press Enter.

4. The Update Records screen contains a list of outstanding update records matching yourselection criteria. If the list is empty, go back to the previous screen and open your searchby using * in client and user, and a date range of 01-01-2000 through 12-31-2010. If youstill get no results, there are no incomplete update records.

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

All records.

6. You will see an Update Updating update requests which have not yet executedpopup. If,after reading this information message, you decide that deleting the update records wouldbe a wiser decision, skip to step 7. Otherwise, click the green picture-icon. You will begiven one last chance 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 force produces an error,or you are unsure whether forcing the update record to completion is the wisest choice,forcing the update may not be an option. If this is the case, deleting the update lock isprobably your best course of action. From the top-most menu of the Update Recordsscreen, click Update records Delete All records. You will be given an opportunity tochange your selection criteria in the Delete Update Records popup. Click the green picture-icon to continue. You will be given one last chance to stop via a Delete data will belostpopup. Click Yes to start the delete.

8. You will not receive a confirmation message after the update or delete. You may nowleave the SM13 transaction.

Return to Index...

Viewing OS Server Files from SAP

The SAP directory structure on a Linux server can be viewed via SAP using the AL11 transaction.All the usual SAP directories are accessible as well as any custom data views. Text files can beaccessed and ported in and out of the SAP instance. Directories can be sorted by Name orDate/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 new instance to theexisting TMS configuration. You could severely damage any pre-existing transports, makingthem untransportable. Instead, use the following section 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.


27/65

.

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.

6. Fill in the TMS: Configure Transport Domain popup with theDescription, Name of DOMAIN_, and the description of the

Transport Domain. Then click Save.

7. On the Transport Management System screen (if you arent there, back out until you are),assuming that this is the first SAP instance and there are no 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 system configuration or PRD ifyou are going to have a two system configuration, or make up a if you are neverreally going to have another SAP system. Fill in the rest of the information including the Pathwhich is assumed to be\\:\usr\sap\trans for NT or /usr/sap/trans for UNIX. Click EnvironmentTransport Routes.

9. On the Display Transport Routes screen, click the User Settings button, turn on the

Hiergraphical List Editor, and click the Continue button. Back out of the screen and then goback in you should see the list in a text mode which makes it easier to handle.

10. On the Display Transport Routes screen, click the DisplayChange button to toggle intoChange Mode.

11. On the Change Transport Routes screen, click Configuration Standard Configuration Developmentand Production System.

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

13. Back on the Change Transport Routes screen, click the Save icon and confirm all thepopup questions.

14. On the Change Transport Routes screen, back out until you can once more see the

Transport Management System screen. Click Overview Systems.15. On the Display TMS Configuration: System XXXscreen, double-click the TMS Domaindomain controller SAP instance.

16. On the Display TMS Configuration: System XXXscreen, click the DisplayChange buttonto toggle into Change Mode. Click the Communication tab and make sure that the TransportGroup Name is correct. It should contain of the Domain Controller in the format ofDOMAIN_ where is the System ID of the SAP Domain controller. Use thedropdown to find the correct entry it the field is blank. Click the Transport Tool tab. Verifythat the information on the tab is correct and click the Insert Row button. Add a Parameterof CTC and a Value of 1. Click the Save button.

17. Do step #16 for every system in your TMS Domain, making sure to change all TransportGroup Names are the same and the CTC row is added to each with a value 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.


28/65

.

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.

6. Fill in the TMS: Include System in Transport Domain popup with theDescription, 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 EnvironmentTransport 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 enterthe SID of the transport domain, create a Z* transport layer, and the SID

of the system you are adding. Click Save and confirm. Back out to the main Transport Management Screen.

12. Back on the Transport Management System screen, click Overview Systems.Double-click on the new system, and click on the Communications tab. Makesure that the Transport Group name is the name of the original transportdomain. If not, change it. Click the Transport Tool tab. Verify that theinformation on the tab is correct and click the Insert Row button. 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 needs fixed.

2. Go to SE03.

3. On the Transport Organizer Listscreen, click on Merge Object Lists which isin the Requests/Tasks section.

3. On the Merge Objects Listscreen, put SM1K00046 in the first Request/Taskfield. Make sure that the Releasedcheck box is "on" in the Request Statussection and click the Execute icon.

4. On the Merge Objects Listscreen, click on the Merge icon.5. On the Enter Transport Requestpopup, click the Create Requesticon.6. On the Select Request Type popup, click "on" radio buttion Workbench Request.7. On the Create Requestpopup, fill in the necessary information and make sure

that the fill in the Targetfield 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 in


29/65

.

directory cofiles copy K00050.SM1 to K00046.SM1, and in directory data copyR00050.SM1 to R00046.SM1.

8. You may now leave SE03.

Once you have control of your session again, the transports are done. Verify their return code inthe Import Queue list. It shoud have been updated automatically.

Return to Index...

Transporting Change Requests

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

1. Make sure the change request(s) has been released via Se10 or one of the otherTransport Organizer Transactions.2. Go to transaction STMS and click Overview Imports. Double-click the PRD queue.3. Click the refresh button to make sure you have the most current view of the PRD queue.Make sure the change request(s) you want to transport shows in the queue.4. Using the F9 button, highlight all the transactions you want to manually transport.5. Click on Extras Activate Inactive Requests. Confirm the popup. This bypasses theSTMS_QA process.

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

Once you have control of your session again, the transports are done. Verify their return code inthe Import Queue list. It shoud have been updated automatically.

Return to Index...

Adding a Change Request to a Transport Queue

1. Make sure the change request(s) has been released via Se10 or one of the otherTransport Organizer Transactions.2. Go to transaction STMS and click Overview Imports. Double-click the PRD queue.3. Click on Extras Other Requests Add. Fill in the Number of the Transport Request tobe added to the queue and then press Enter.4. Confirm the Add Transport Request popup. The transport request should now appear atthe bottom of the queue list.

Return to Index...

Viewing the Transport Queue History

1. Go to transaction STMS and click Overview Imports. Double-click the queue for whichyou want to view the history.2. Click on the Import History button or press Ctrl+F7. The resulting list can be sorted andfiltered to produce a more exacting report if needed.

Return to Index...

Re-Transport Several Change Requests at Once

1. Go to transaction STMS and click Overview Imports. Highlight the queue into which thetransport(s) to be moved again were originally transported the FROM queue - and clickthe Import History button or press Ctrl+F7.


30/65

.

2. If your SAP instance is older, you may have a very long Import History list in the next screen.Use some of the available filters and sort options to create a more controllable list oftransports. Use the F9 to select and/or unselect as many as you need to transport.

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

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

Return to Index...

Transport Tool System Confirmation

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

a message asking if you want to check the the transport tool for all systems. If only want tocheck a limited subset of the SAP instances, use F9 to select and/or deselect those systemsbefore you click Transport Tool.

3. On the TMS: Check Transport Tool screen, a list of all selected SAP instances to be checkedwill appear.If you see any thing but red green Oks, expand all the lines with the non-OK marks and lookfor more information. Correct these problems and then run this report again until it comes

back clean.

Return to Index...

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

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

Routes.

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 Assignmentbutton. 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 topicUsing Target Groups to Transport to Mulitple Clients in Two Different Instancesto fulfill the a) requirement.


31/65

.

1. Log on to client 000 of your TMS Domain Controller SAP Instance.

2. Go to transaction STMS.3. On the Transport System Managementscreen, 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. Under

Transport Routes, click on the QAS instance and click Create.5. On the Create Transport Route screen, make sure Deliveryis "on" and fill in

Source 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 Assignmentbutton. 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 and

click 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 Managementscreen, 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 ImportAll Requests button.

5. On the Start Importpopup, 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/65

.

Creating, Modifying, and Deleting Users

Creating a User

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

2. Go to transaction SU01.

3. On the User Maintenance: Initial Screen screen, type in the new User name and click theblank page picture-icon.

4. On the Maintain Userscreen, fill in at least the following information for each 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 the screen. Youmay 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 be changed.


3. On the User Maintenance: Initial Screen screen, type in the User name to be copied andclick the double blank page picture-icon.

4. On the Copy Userpopup, type in the To for the new user and click the Copybutton.

5. On the Maintain Userscreen, click on the tabs and make the changes to the usersinformation. When you are done, click the Save picture-icon. You will receive a User

savedmessage in the status bar at the bottom of the screen.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.


9. On the User Maintenance: Initial Screen screen, type in the users name and click thepencil 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. Youmay now leave the SU01 transaction.

Return to Index...

Deleting a User

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



33/65

.

3. On the User Maintenance: Initial Screen screen, type in the users name and click the trashcan picture-icon.

4. On the Delete userpopup, click the Yes button.

5. You will receive a User deletedmessage in the status bar at the bottom of the screen. Youmay now leave the SU01 transaction.

Return to Index...

Locking a User

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


3. On the User Maintenance: Initial Screen screen, type in the users name and click thelock/unlock picture-icon.

4. On the Lock userpopup, click the lock picture-icon.

5. You will receive a User lockedmessage in the status bar at the bottom of the screen. Youmay now leave transaction SU01.

Return to Index...

Modifying a Users Password

1. Log on to the appropriate SAP system and the client where the users password is to bechanges.


3. On the User Maintenance: Initial Screen screen, type in the users name and click thelock/unlock picture-icon.

4. On the Change Passwordpopup, enter the new password in both the New passwordandRepeat passwordboxes. Click the green picture-icon.

5. You will receive a The password was changedmessage in the status bar at the bottom ofthe screen. You may now leave the SU01 transaction.

Return to Index...

Add a Role to a User

1. Log on to the appropriate SAP system and the client where the user needs the role. Go totransaction SU01.

2. On the User Maintenance: Initial Screen screen, type in the users name and press Enter toconfirm that the user exists.

3. Click the Change button or press Shift+F6.

4. On the Maintain Userscreen, click on the Roles tab. Fill in the name(s) in the field(s)

provided, and when done press Enter.5. Click the Save button.

6. Go to transaction PFCG, and on the Role Maintenance screen, type in the name of the roleto which the users where added and press Enter to confirm exist of the role.

7. Click the Change role little yellow pencil button.

8. On the Change Roles screen, click the Usertab. Click on User Comparison and thenComplete Comparison. Once the comparision is done, click Save one more time and youare done!

Return to Index...


34/65

.

Mass User Changes

Making user changes one-at-a-time can be extremely time consuming not to mention boring.SAP has provided mass change transaction to help eleviate the tediousness of making many userchanges. It should be noted, however, that the mass change transaction is limited as to thechanges that can be made. For example, you cannot change the password for multiple users.Also note that it is best to make one type of mass change at a time. For example, you need toadd a new role to and delete an existing role from 20 users. The best method to achieve this

would be to first do a mass change to add the new role. Save the changed users. Then deletethe existing role from the same 20 users.

1. Log on to the appropriate SAP system and the client where the user changes are to takeplace.


3. On the User Maintenance: Mass Changes Initial Screen screen, you need to select whetheryou will select users based onAddress Data orAuthorization Data and click the appropriatebutton. If you clickAddress Data, you can find users with any combination ofFirst name,Last name, User ID, Company, City, Building, Room, Extension, Department, and CostCenter. If you opt to useAuthorization Data, you can specify a combination ofGroups,Reference User, Authorizations, Athorization Objects, and many other fields. For eithermethod, fill in the fields you want to search on in the Users by Complex Selection Criteria

screen, and click the Execute button.4. On the Users by Complex Selection Criteria screen, you can click on the users to be

changed, or click the Select All button. Once all the users you want to change have beenselected, click the Transferbutton.

5. Back on the Maintenance: Mass Changes Initial Screen screen, you can select all the userson the screen again by clicking the Select All button or change your mind and make anylast minute corrections. Once you have all the users selected that you want to change,click User Change.

6. On the Mass User Changes screen, scroll through the tabs, changing data and clicking theAddor Remove button for each correction. Please note, each SU10 batch run must use allAdds or all Removes but never a mixture. Do allAdds in one run and then all Removes inanother. Once all your changes have been made, click the Save button.

7.On the Mass changes popup, you will see how many users you are about to change. Tomake the changes, click on Yes.

8. On the Log Displayscreen, you will see a log of the changes you made. Expand the list tosee the transactional details.

9. You may now leave the SU10 transaction.

Return to Index...

User Information Repository Reports

1. Log on to the appropriate SAP system and client where the user reports are to begenerated.

2. Go to transaction SUIM.3. On the User Information System screen, click the Infosystem authorizations entry on the

navigation tree and click the double arrows pointing down picture-icon to expand the list ofavailable reports.

4. Click on the clock picture-icon to the left of the re

90959 basis operations unix linux

Documents