Patent available for licensing

Computer Input and Pointing Device

United States Patent D601,566

User Information System from SU01

To get quick User related information in an SAP System:

1. Go to transaction code SU01
2. From the upper menu, click on 'Information'
3. From drop-down menu, click on 'Information System'
4. You should see a Menu Tree showing various User Admin areas such as:

• User
• Roles
• Profiles
• Authorizations
• Authorization Objects
• Transactions
• Comparisons
• Where-Used List; and
• Change Documents

Browse through the above and you will realize there are so many User/Security admin tasks you can perform from here!

Backup Domain Controller in SAP TMS Landscape

How to assign a Backup Domain Controller in TMS?

1. Logon to your Domain Controller SAP System in client 000
2. Execute Transaction Code: STMS
3. Click on the icon System Overview, alternatively click on Overview from the top menu and then click on Systems
4. Select your Domain Conroller system, double click
5. You will see three tabs: Management, Communication, and Transport Tool
6. Click on Communication
7. Click on Edit
8. You will see Backup under Transport Domain
9. Select your Backup Domain Controller system in this area
10. Save the configuration
11. Verify/Chanage the settings in remaining systems accordingly and Distribute the changes in All systems in your TMS landscape
12. Should you wish to test the functionality, bring your Domain Controller down and your backup domain controller should be promoted to the Domain Controller
13. Once your original Domain Controller system comes back online, your promoted Backup Domain Controller system should then assume the original role of Backup Domain Controller.

Good luck!

Two Important Traces in SAP Systems from Admin point of view

System Trace

• Transaction Code: ST01

Performance Trace

• Transaction Code: ST05

Your S-User in SAP Solution Manager System

How to Associate your S-User in SAP Solution Manager System?

Use Transaction code: AISUSER

Change View "SAP Support Portal Contact Person Assignment": Overview

1. Keep an S-User number handy, no Zeros
2. Click on New Entries
3. Enter User ID (you SAP System Logon ID) and S-User number in 'Contact Person' field
4. Save it!
5. Go back and check for the entry that you just created
6. Test it!

Good luck!

How to Undo changes already inclued in a Transport Request

Scenario:

1. An SAP BI system landscape
2. You have three systems, DEV, QAS, and PRD
3. You have a stand-along system SBX (Sandbox System)
4. You don't have any backups scheduled on SBX
5. You are making some changes in SBX
6. You keep including those changes in a transport request in SBX
7. At one point you realize that some or all of those changes in a particular transport request isn't necessary or they MUST be reverted.

What would you do?

Following is what you can do:

Option One: If backups are scheduled and available by any chance, then restore the system, point-in-time to the original state.

OR

Option Two: Undo those changes, manually. One by one, which could be very time consuming.

OR

Option Three: Find the original obejcts from either of DEV, QAS, and PRD systems and collect them in a transport request and move that request to SBX at OS level.

Good luck!

VMC System Administration

Use Transaction Codes

SM53
SM52

Move a Released Local Transport Request

How to move a Released Local Transport from One SAP System to another SAP System?

Scenario:

1. Locally created transport request (Customization Request)
2. Request gets released
3. Need to move to another SAP system in transport landscape
4. Create a new Customization Request
5. Add objects
6. Add that Locally created and released transport request number to include into this newly created Customizing Request
7. Make sure that target shows the target group or target SAP system and client thereof
8. Release the task of this new request
9. Release this new request
10. Refresh import queue of your target SAP System
11. Then import this request!

How to See Processes from All Users in Windows

1. Open Windows Task Manager (Ctrl+Alt+Del)
2. Click on Processes
3. Click on 'Show processes from all users on the bottom of the window.
4. Refresh!

Logon Load Balancing

1. Install all application server/dialog instances


2. Configure Logon Group using transaction SMLG


3. Assign proper instance, check mark Ext. RFC enabled, provide reponse time and number of users


4. Click on Copy


5. Do the same for all Instances


6. Save


7. Go to your system directory, system32\drivers\etc\services file


8. Add the following entry


9. sapms 39xx/tcp


10. The above port number should be the same what you used as Message Server port during your Dialog Instance installations


11. Go to your SAP GUI logon pad


12. Configure your connection details as following:


13. Create or Modify by clicking New Item or Change Item


14. Provide Description


15. Provide System Id


16. Provide Message Server


17. Move to Group/Server tab and the Logon Group you created should become visible there along will all app servers and what processes they have


18. System Number should come automatically as well


19. Click OK

Test the logon!!!

How to apply MSSQL Patch/SP for DB in SAP System

SAP System
DB - MSSQL
OS - Windows Server


Straight and Simple:

1. Download the patch from SAP Service MarketPlace
2. Stop SAP using MMC
3. Stop DB using MS Visual Studio
4. Stop all SAP Services from service.msc
5. Stop all SQL Services from service.msc
6. Close MMC console
7. Close MS Visual Studio console
8. Drill down the installer for your OS/HW from the downloaded media, i.e. x64, x86, etc.
9. Double Click the installer
10. Let the installer check if any conflicting services are running or not
11. Complete the installation
12. Check DB/Bring DB online
13. Check SQL services/Start SQL services from service.msc
14. Start SAP services from service.msc
15. Start SAP using MMC

SQL Patching is done!

Check and confirm SQL patch number from MS Visual Studio.

Good luck!

Shival

Dialog Instance Installation

Short and Sweet scenario:

SAP System: SAP CRM 5.0
OS: Windows 2003 Server R2, SP2
DB: MSSQL 2005, SP3

I have a newly installed central instance up and running

Now, I upgraded the kernel.

Now, tried installing Dialog Instance and got the error of "disp+work" not starting up.

Following is what worked!!

1. Restored the original kernel files.
2. Uninstalled the progressed installation of DI
3. Re-initialized DI installation.

And it went through!

###############

Now I upgraded kernel on Central Instance.

DI Dialog Queue became unavailable.

Following is what worked!!

1. Stop MMC on Dialog Instance
2. Stop sap_NN service
3. Close MMC window
4. Close service.msc window
5. Physically Copy 'sapstartsrv.exe' from Central Instance.
6. Rename 'sapstartsrv.exe' under Windows\system32 (being conservative)
7. Paste 'sapstartsrv.exe' to this location.
8. Open MMC window
9. Start SAP
10. The above should work just fine!!!

Try referring following SAP Notes for digging this deeper!!!

1. sapnote_0000035278 - STARTSAP-STOPSAP - TIME OUT no system connected
2. sapnote_0000072248 - In NT Dispatcher in status Yellow - SAP system running
3. sapnote_0000142100 - Windows Problems with new SAP service as of Rel. 4.5B
4. sapnote_0000396309 - Dispatcher remains yellow, although the system is running

Good luck!

Shival B. Tailor
sbtailor@gmail.com