Wednesday, May 11, 2011

Remodeling in SAP BI 7

Before the release of SAP BI 7.0, in the previous version 3.x; we were not able to redesign the info cubes without deleting the existing data from the info cube. We had to delete all the data, modify the cube & then re-load the data again. But with the release of 7.0; the concept of Remodeling introduced as a feature to change the design of an info cube without deleting the Existing Data.



Before starting with the steps of Remodeling, I would like to mention the Dos & DONTs –

No data loading should be in process :


After remodeling, check all the BI objects that are connected to the InfoProvider like transformation rules, MultiProviders, DTPs have been deactivated. You have to re-activate these objects manually.


The remodeling makes existing queries that are based on the InfoProvider invalid. You have to manually adjust these queries according to the remodeled InfoProvider.


You cannot replace or delete units. This avoids having key figures in the InfoCube without the corresponding unit


Following are the steps to be followed :
Go to the context menu of Info cube that is to be redesign, select Remodeling as shown in fig. or select the Administration tab from the Left Most Area. There you can select Remodeling or can go direct to the T-Code RSMRT.

Also remember to activate the Transformation as well as the DTP of the Info Cube. Now there you can map the new Info Objects in the transformation but no need to upload the whole data again.


In the similar way, we can delete the Characteristics from the info cube without deleting the existing data into the Info Cube.


Monday, April 25, 2011

SAP Admin Tricks & Tips.

1. Problems with username/passwords while setting JCO's?... try with the password in UPPERCASE.

2. Going home in a hurry?, use transaction /nex to close all your sessions at the same time in specific application server you are logged-in.

3. In an R/3 screen, use %pc to download any TCode full page in any format you want.(.htm, .txt etc). Also use TCode /nSO21 to specify the default download location (this is very useful as saving all files to the sapworkdir can be little annoying at times)

4. Show Work Process usage over time by running SM50 -> List -> CPU. This shows CPU usage in minutes since startup. If all of your DIA WP's show time, then consider adding more.

5. If you want to select text on your SAP screen and if you are not able to do it. use Ctrl+Y and then you can select text.

6. To access history of Tcodes used, click on the Tcode command field and use UP and DOWN arrow keys.

7. To display the checked object when not authorized call transaction SU53. It reports the last objects verified and also the respective values. Incase missing authorization through pop-up then close it (click cross mark) instead of continue it. Then run SU53 immediately either in same session (/nSU53) or in new session (/oSU53).

8. Use ctrl+? to go to the tcode command field on SAP screen.

9. Enter /i on tcode field to delete the current session.

10. Enter /nend to cancel all SAP sessions and log off.

11. Use ALT+F+W and ALT+F+U in SAP Easy Access Screen to download and upload the user favorites within/across systems.

12. To send a SAP message to another person use Function Module TH_POPUP from transaction SE37.

13. Ctrl & + to open new SAP session

14. ctrl+shift+F8 System Administration information.

15. Open SAP Notes on Windows via Batch File

Here is a quick tip on how to open a SAP Note by just typing in or pasting the SAP Note number. Its very convenient, when you are reading a PDF document (possibly a installation/configuration guide) and you come across interesting SAP Notes that you want to quickly check.
Create a batch file using your notepad with the following text:
@ ECHO QUICK COMMAND TO DISPLAY SAP NOTE

@ ECHO ----------------------------------------
@ SET /P sapnote=Please provide SAP Note number ?
@ START /MAX iexplore -new https://service.sap.com/sap/support/notes/%sapnote%?nlang=E
@ PAUSE
Next Create a shortcut to the batch file and put it on your desktop.
Next time you wish to open a SAP Note, simply click on the shortcut and you should get a prompt like the following:
QUICK COMMAND TO DISPLAY SAP NOTE----------------------------------------Please provide SAP Note number ?
Here provide the note number and press the enter key.
The command will fire up a new internet explorer window and open the SAP Note in it. It will help if you have SSO setup for your OSS Userid as you wouldn't need to enter your userid and password.
Hope that helps.

Friday, April 22, 2011

SAP System Administrators are Aliens ?

Do SAP system administrators originate from an Alien civilization?

Introduction
Honestly, I think so but there is no hard evidence just yet. In fact the whole human race could be originating from Alien civilization. There are a lot of facts and small pieces of the puzzle and hopefully one day the puzzle is put together and humanity will know how it all got started. Whatever our origin is we are here now and we are evolving, learning and getting ready for some amazing years where we will see science come up with such breath taking technologic breakthroughs it will be hard to imagine in fifty years how we lived today.


What the … Am I blogging about?
I guess some of you are already wondering if I had magic mushrooms for breakfast by now but I can assure you I did not. I stumbled upon
a video on youtube featuring Erich Von Daniken. I really love it when a video or a blog makes me think and that is exactly what the video did. After watching the video I went to look for more content on whether or not aliens ever where in fact on earth or even if we originate from alien civilization. I found a documentary from history channel and it is in fact very interesting.

In one of my previous blogs “Dumb Poetry of a wise SOAL..!!!” – copy found in
http://bit.ly/fUVUMj you can find hints that how dumb I was. How does any of this relate to basis administrators? I invite you to read on and find out the answers.

We are who we are
System administrators are often stereotyped as being geeky and asocial. A stereotyping I dislike a lot but sometimes I cannot get around the fact that some of my beloved out of work activities seem to fall in that category. Although the gaming industry is much larger than the movie industry these days gamers are also stereotyped as being geeky. So I already have my profession that points in the direction of being geeky and then I have the fact that I love playing games. Wait is that a bad thing really? Geeky is hot nowadays, the huge geeky looking glasses are worn by some hipsters and geeks seem to be attractive somehow.

I do believe a lot of diverse persons exist within a single profession but I also see similarities. Of course everyone has its own personality and looks different and I’m glad that is a fact. How boring would the world be if everyone would have the same personality and look exactly the same? Seriously, I wouldn’t want to have a girlfriend that looks like a copy of someone else.

A similarity I often see among SAP system administrators is that they are dedicated and flexible. We tend to have very flexible work hours and it is also something we love. I do love the fact that I can do irregular work hours, especially if I can start at five am. Of course the job also brings along timings or tasks that are less interesting. Working during weekends or being called in the late evening because a SAP system has crashed for example. When we are on guard we can be called 24/7 in case something goes wrong.

The importance of flexibility
There is a lot of unawareness what system administrators do and it also brings some what I call “crazy eye” looks along with the unawareness. Sometimes to others it looks like we are not working hard, for example when I would be leaving the office at two pm. But that is because the other people in the office don’t know that I was awake at five am solving an issue and started to work already. It can also be the case that I have to do more work at seven pm again from home.

As a SAP system administrator being flexible is important. It makes sense that the business doesn’t want to bring down their productive SAP system during the work hours or even extended work hours so it also makes sense as a system administrator you will sometimes be working in the evenings, at night or in the weekend.

Working twenty-four hours straight
I’m planned in to do a SAP upgrade in one of these weekend and not to my surprise I’m being misunderstood by my own better half who has been feeling slightly ill this week. As some of you already read I have two children (Karim, 18 months old and Ishrath Nine years old) and it can be exhausting to keep them busy so I can understand it isn’t easy.

Being a SAP system administrator means you have to constantly keep learning to avoid your contract being cut off and ending up losing your job in the worst case scenario. Last week I attended a Cloud Computing of SAP to broaden my knowledge and get in touch with Cloud Computing. Of course I ended up coming home very late because I had started at five thirty pm. I arrived back home at around six pm and my daughter is asking where are you been.!!! I have a self-defense class today do you know that ?

I know I will be called at any time when I’m on-call or to start working on the upgrade. I also know it is going to be a lot of work since it is a large, distributed environment with a lot of dependencies. It is also a very business critical mission because it is one of the most important SAP systems in use. Given this and all the tasks that I will be performing, taking into account the durations of all of the different tasks I performed on the Q A landscape I know up front I’m looking at staying awake for more than twenty-four hours straight.

It is a necessity to ensure I will be ready on schedule so functional testing can begin once I have finished my work. This is also part of being a system administrator. Later on the day I will finish the latest preparations so I can start tonight and have a smooth upgrade. Of course I’m not the only one involved in general for the upgrade but to perform the technical upgrade of the SAP system and everything connected to it that is depending on it I am.

Alien language
Sometimes I really feel as if I’m talking in an Alien language as my better half has a hard time understanding why I have to work at certain timings or why on earth I have to stay awake for twenty-four hours if needed. Can’t you just check every few hours? No it doesn’t work like that.

I want this upgrade to succeed and I don’t want to lose time that can be spend on performing proper testing before the actual Go Live. It can feel like talking to a brick wall but then again my better half seems to have the same feeling. No matter how far my explanation goes that it is a necessity and that it is of great importance the misunderstandings and the crazy eyes seem to stay.

System Administrators Attention
I hope this blog and other blogs about SAP System Administration or also referred to as Basis Administration can give a view on what we do and get rid of some of the stereotyping and misunderstandings. I’m glad to see other community members, start to bring system administration into the picture by producing content on this Blog.

I was also very pleased with the SAP Virtualization and Cloud week that did contain sufficient information for SAP system administrators. It was very interesting and in my opinion also very much needed as we still have to search really hard sometimes to find sufficient information. I still see a lack of system administration related content in certain events but I will keep voicing the need for content and also for a system administration space.

I also still invite everyone to use the hashtag #sapadmin to mark interesting content on twitter for system administrators.

I do what I have to do
I’m glad I was able to vent my frustration by writing this blog which is actually a great way to vent. I’m dedicated to the cause and I will do whatever it takes to make this upgrade a success story.

This is what a system administrator has to do and it is one of the reasons that make us valuable.

Tuesday, December 7, 2010

Clustering in SAP Systems

Steps for High Availability Failover Clustering for SAP Systems
1)Configure the Internal Disks RAID configuration
2)Fill in general worksheet with values like IP Addresses (7 IP addresses, 2Private Network, 2Public Network, 3Virtual)
3)Install OS (Windows Server 2003) on Node A
4)Install OS (Windows Server 2003) on Node B
5)Modify BOOT.INI on NodeB (Change the timeout =5 in the boot loader file so that there is no simultaneous contetion of shared drives)
6)Configure disks directories on RAID1
7)Storage Manager configuration (Fibre channel configuration)
8)MSCS pre install verification
9)configure the server service change memory parameter to zero
10)Set the page file size to 5 times the RAM size
11)Modify the BOOT.INI for 4GB tuning NOT NEEDED
12)Remove drivers and protocols Remove unnecessary drivers or disable them (Spooler), only one protocol TCP/IP is needed,
13)Install MSCS on NodeA at end of installation reboot NodeA
14)Install MSCS on NodeB at end of installation reboot NodeB
15)Installation of troubleshooting tools MOM
16)Windows NT service pack installation
17)DNS and transport directoy configuration On the transport host create the directory \usr\sap\trans If no instance will be installed on the transport host share this directory as SAPMNT
18)Installation of IE, MMC, page etc
19)Install the latest SAP Kernal patches
20)Apply the post SP4 DLLs Latest Windows cluster patches
21)Correction of Network bindings Test the host files i.e move the groups from one Node to the other. Ping response should come from the public network, Chnage the order in which the cards are listed as:1)Public Network, 2)Backbone Network, 3)Private Network
22)MSCS verification test the service using the CASTEST utility, power down one of the nodes and check the logs.
23)Create the installation user account
24)Installing SAP and the DBMS
*Preliminary Work Filling in all the details from worksheets.
*SQL Server Install- Install SQL Server on NodeA Start SQL Server on NodeA -Register ServerA- Perform simple queries- Stop SQL Server
* Install service pack on NodeA
*Install R/3 setup tool From SAP kernal start the program Sapinst.exe
*Install SAP R/3 Central Instance and Database Instance give necesary parameters, This will take several hours, Reboot NodeA
* Run the cluster Failover wizard on NodeA Start=>Programs=>SQL Server=>Failover Cluster Wizard. Here give SA Password, SQL Service Account, IP Address (VIRTUAL IP FOR ACCESSING THE DATABASE ON THE PUBLIC NETWORK), Server Name (ITSSQL)
After installation reboot NodeA and NodeB
When system restarts log on to NodeA as Installation user (sapinst)
Move all resources back to NodeA
Configure two shares SAPLOC and SAPMNT pointing to \USR\SAP
Restart the windows services: SAPOSCOL and SAP
Restart the databse service in the cluster administrator
All the resources for SQL Server are now displayed in the cluster Administrator anc can be moved between Nodes.
*SQL Server cluster conversion
Install the Cluster Conversion tool on NodeA, provide SAPSYSTEMNAME ITS, \users\adm\install, it will ask do you want to logoff yes
Now Install cluster conversion tool on NodeB
SAP Cluster conversion:
Creates the SAP cluster group
■ Copies tools to the SAPCluster directory
■ Sets the SAPService to manual
■ Makes sure that the SAPOsCol service is started from the SAPCluster directory

Thursday, July 2, 2009

SAP Basis Administrator Transaction Codes (TCodes)

Daily maintenance
SM12 Lock entries
SM21 System Log
SM37 Check the batch jobs
SM50/51 Show all processes on one server / all servers
SM66 Show all active process on the system
ST11 Display developer-traces
ST22 ABAP-dumps
ST06 OS Monitor
ABAP Related
SE11 ABAP dictionary
SE16/SM30 Data browser/Table editor
SE37 Function builder
SE38 ABAP editor
SE41 Menu painter
SE51 Screen painter
Background job related
RZ04 Operation modes
SM36 Create background job
SM37 Show background jobs
SM63 Operation mode calendar
SM65 Check background job-settings
SO15 Distribution list creation
SM62 Event creation
Useful admin tcodes
AL11 SAP directories
DB01 DB Exclusive locks
DB02 Database performance: Tables and Indexes
PFCG Profile generator
RZ10 Profile maintenance
SARA Archiving
SCC4 Client change options
SE01 Transport organizer, use SE09 for ABAP-transports, SE10 for customizing transports
SE06 (4.x up) System change options, see SCC4 for Client change options.
SE71 Maintain Layout-sets also known as sapscripts
SM02 System message
SMGW Gateway administration
SMLG Define logon-groups
SMLT Language administration
SPAM Support Package Manager
SPAU ABAP-dictionary assistant during support package-import
SPDD Data-dictionary assistant during support package-import
STFK Search the customer system that have an open connection to Walldorf
SM01 Lock transactions
SO01 SAP Office Workplace
RSPRECADMIN BW Pre calculation Service Status
SAP R/3 Transaction Codes V2
Alert Monitor Transactions
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL03 Operating system alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL06 Performance: Upload/Download
AL07 EarlyWatch Report
AL08 Users Logged On
AL09 Data for database expertise
AL10 Download to Early Watch
AL11 Display SAP Directories
AL12 Display table buffer (Exp. session)
AL13 Display Shared Memory (Expert mode)
AL15 Customize SAPOSCOL destination
AL16 Local Alert Monitor for Operat.Syst.
AL17 Remote Alert Monitor f.Operat. System.
AL18 Local File System Monitor
AL19 Remote File System Monitor
AL20 Early Watch Data Collector List
ALDB Logical Databases
Database Monitor Transactions
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes in DB
DB03 Parameter changes in database
DB11 Early Watch Profile Maintenance
DB12 Overview of Backup Logs
DB13 Database administration calendar (Backup). SAPDBA In Unix
DB14 Show SAPDBA Action Logs
DB15 Check the sizing of the objects in DB
DB16 Trigger/browse infcfgcheck protocols
DB20 Check the size of one specific table
Operating System Monitor Transactions
OS01 LAN check with ping
OS02 Operating system configuration
OS03 O/S Parameter changes
OS04 Local System Configuration
OS05 Remote System Configuration
OS06 Local Operating System Activity
OS07 Remote Operating System Activity
OS11 Spare Part Indicators
OS12 Material Provision Indicators
OS13 Item Categories
OS14 Material Types Allowed in BOM Item
OS15 Variable-Size Item Formulas
OS16 BOM Item Object Type
OS17 Explosion Types
OS18 Relevancy to costing
OS20 BOM Usage
OS21 BOM Usage Default Values
OS22 Copying Defaults for Item Statuses
OS23 BOM Statuses
OS24 Material Types Allowed in BOMs
OS25 BOMs with History Requirement
OS26 Laboratory/Office
OS27 Modification Parameters for BOMs
OS28 Defaults for BOMs
OS29 User-Specific Settings for BOMs
OS30 Application
OS31 BOM Usage Priorities
OS32 Alternative BOM Determination
OS33 Alt. Determination in Inventory Mgmt
OS34 Alt. Determination in Costing
OS35 Alt. Determination in Production
OS36 Alt. Determination in SD
OS37 Alt. Determination in PM
OS38 Alt. Determination in MRP
OS40 Generate BOM Transfer File
OS41 Transfer BOM without Long Text
OS42 Process Transfer File
OS43 Copy BOM changes
OS44 Copy BOM variants
OS45 Copy BOM with description
OS51 Change Master Statuses
OS52 Change Master Match code
OS53 Number Ranges for Change Masters
OS54 Change Master Control Data
OS55 Material Revision Level Sequence
OS56 Change Types
OS57 Document Revision Level Sequence
OS58 Object Mgmt Record Change Types
OSC1 Appoint. Diary: Maint. Appoint. Type
OSC2 Appoint. Diary: Maint. Destination
OSFI File names
OSG Command file for customizing graph.
OSP1 Settings for Repet.Manufacturing
OSP2 Repetitive mfg profile
OSP3 Back flush Data for Repet.Manufact.
OSP4 Repetitive mfg: distribution function
OSP5 Repetit.Manuf: Cost Log
OSP6 Create Cost Collector Strategy
OSP7 Withdrawal sequence
OSP8 Number Range for Backlogs
OSP9 Number Range for Document Log
OSPA Customizing Distribution Function
OSPB Customizing Production Order Type
OSPC Customizing Goods Movements
OSPD Customizing Planning Periodicity
OSPE Marinating No. Ranges for RS Header
OSPF Repetitive Manufacturing Line Texts
OSPG Copy Repeat. Manufacturing Line Text
OSPI Number Range for Backflush Discrep.
OSPJ No. Range Interval for Document Log
OSPK Storage location search
OSPL Movement Types
OSPM Background Job Reprocessing REM
OSS1 Logon to Online Service System
OSSC Appoint. Diary: Maint. Appoint. type
OSSZ CPP Authorizations
OST1 CS Transport C Tables TCS21/TCS22
OST2 CS Transport C Tables BOM Usage
OST3 Transp. Customizing tabs T418F, T418G
OSU1 su: Display Export Filter
OSU2 su: Display page formats
OSU3 su: Display Postscript fonts
OSU4 su: Display screen fonts
OSU5 su: Display colors
OSU6 su: Display shapes
OSU7 su: Display line types
OSUR su: Customizing profile
OSSN1 SAP FTP desde donde se puede acceder a SAP.
Computing Centre Transactions
RZ01 Job Scheduling Monitor
RZ02 Network Graphics for SAP Instances
RZ03 Presentation, Control SAP Instances
RZ04 Maintain SAP Instances
RZ06 Alerts Thresholds Maintenance
RZ08 SAP Alert Monitor
RZ10 Maintenance of profile parameters
RZ11 Profile parameter maintenance
RZ12 Maintain RFC server group assignment
RZ15 Read XMI log
RZ20 CCMS Monitoring
RZ21 Creating and changing CCMS properties
RZE1 Central rules per object
RZE2 Where-used list: Central rules
RZEN Where-used list central rules
System Menus
S000 System Menu
S001 Workbench Menu
S002 Menu Administration
Systems Transactions
SA01 Number range maintenance: ADRNR
SA02 Academic title (cent. addr. admin.)
SA03 Title (central address admin.)
SA04 Name prefixes (centr. addr. admin.)
SA05 Name suffix (centr. addr. admin.)
SA06 Address or personal data source
SA07 Address groups (centr. addr. admin.)
SA08 Person groups (centr. addr. admin.)
SA09 Internet. versions address admin.
SA10 Address admin. communication type
SA38 ABAP/4 Reporting( Sequence of changing values at SAP startup).
SA39 SA38 for Parameter Transaction
SABB ABAP/4 Manual: Flight Booking
SAD0 Address Management call
SADC Address: Maint. communication types
SADP Init.scr. addr.maint.person in comp.
SADR Address maint. - Group required!
SADV International address versions
SADX Directory exchange
SALE IMG Application Link Enabling
SAMT ABAP/4 Program Set Processing
SAR Maintain Transaction Codes
SAR0 Display Standard Reporting Tree
SAR1 Structure of an archive object
SAR2 Definition of an archive object
SAR3 Archiving: Customizing
SAR4 Definition of the archive classes
SAR5 Assignment of archive classes
SAR6 Archive events: Generation program
SARA Archive management
SARL Call of Archive Link Monitor
SARP Reporting (Tree Structure): Execute
SART Display Report Tree
SAX4 Addresses: X.400 addresses generated
Client Administration Transactions
SC38 Start Report (Remote)
SCA1 Cannot be executed directly
SCA2 Cannot be executed directly
SCA3 Cannot be executed directly
SCAL Factory Calendar with GUI
SCAM CATT Management
SCAR Record CATT procedures
SCAT Computer Aided Test Tool
SCC0 Client Copy
SCC1 Client Copy - Special Selections
SCC2 Client transport
SCC3 Client Copy Log
SCC4 Client Administration
SCC5 Client Delete
SCC6 Client import
SCC7 Client import – post processing
SCC8 Client export
SCC9 Remote client copy
SCCL Client import - post processing
SCD0 Change Documents for Utilities
SCDN Change Documents for Number Ranges
SCDO Display Change Document Objects
SCOA SAPconnect: Administration
SCOM SAPcomm: Configuration
SCON SAPconnect: Configuration
SCPF Generate enterprise IMG
SCT1 Logical imports - overview
SCU0 Table Analyses And Comparison
SCU1 Table Comparison - Export to Tape
SCU2 Table Comparison Against Tape
SCU3 Table History
SCUI Communicate system status to SAP
Workbench Transactions
SE01 Transport and Correction System
SE02 Environment Analyzer
SE03 Transport Utilities
SE06 Set Up Workbench Organizer (Change the write system status)
SE07 Transport System Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE12 ABAP/4 Dictionary Display
SE13 Maintain Technical Settings (Tables)
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser
SE17 General Table Display
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP/4 Editor. Export-Import objects, sequence changed values
SAP startup.
SE39 Split screen Editor: Program Compare
SE40 MP: Standards Maint. and Translation
SE41 Menu Painter
SE43 Maintain Area Menu
SE44 Hierarchy Display
SE48 Program Analysis: Call Hierarchy
SE49 Program Analysis: Table Manipulation
SE51 Screen Painter
SE52 Parameterized screen painter call
SE54 Generate table view
SE55 Internal table view maintenance call
SE56 internal call: display table view
SE57 internal delete table view call
SE61 R/3 Documentation
SE62 Industry Utilities
SE63 Translation
SE64 Terminology
SE65 R/3 Doc. Short Text Statistics
SE66 R/3 Documentation Statistics
SE68 Translation Administration
SE71 SAPscript layout set
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Repository Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE89 Maintain Trees in Information System
SE90 Process Model Information System
SE91 Maintain Messages
SE92 Maintain System Log Messages
SE93 Maintain Transaction Codes
SE95 Customer Enhancements to AEW Objects
SEPS SAP Electronic Parcel Service
SERP Reporting: Change Tree Structure
SEU Object Browser
System Maintenance Transactions
SM01 Lock transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM21 System Log. Errors and inconsistencies (alert.log.)
SM22 Errors and inconsistencies in the operation modes.
SM28 Installation Check
SICK SM28
SM29 Model Transfer for Tables
SM30 Call Up View Maintenance
SM31 Table Maintenance
SM32 Maintain Table Parameter ID TAB
SM33 Display Table Parameter ID TAB
SM34 View cluster maintenance call
SM35 Batch Input Monitoring
SM36 Define Background Job
SM37 Background Job Overview
SM38 Queue Maintenance Transaction
SM39 Job Analysis
SM49 Execute Logical Commands
SM50 Work Process Overview
SM51 List of SAP Servers
SM54 TXCOM maintenance
SM55 THOST Maintenance
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM61 Display Background Processing Components
SM62 Display/Maintain Events
SM63 Display/Maintain Operating Mode Sets, Scheduling.
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM66 Systemwide Work Process Overview
SM67 Job Scheduling
SM68 Job Administration
SM69 Display/Maintain Logical Commands
SMEN Dynamic Menu
SMGW Gateway Monitor
SMLG Maintain Logon Group
SMLI Language Import Utility
SMLT Language Transport Utility
SMME Output control Message Block Table
SMO1 Repository Information System: SMOD
SMO2 Repository Information System: SMOD
SMO3 Repository Information System: SMOD
SMO4 Repository Information System: SMOD
SMO5 Repository Information System: SMOD
SMOD SAP Enhancement Management
SMPC Translation Interface PC - R/3
SMW0 Maintain World Wide Web Objects
SMX Display Own Jobs
Spooling Transactions
SP00 Spool and Related Areas
SP01 Output Controller
SP02 Display Output Requests
SP03 Spool: Load Formats
SP11 TemSe directory
SP12 TemSe Administration
SP1T Output Control (Test)
SPAD Spool Administration
SPAM SAP PATCH MANAGER (SPAM)
SPAT Spool Administration (Test)
SPAU Display modified DE objects
SPBM Monitoring parallel background tasks
SPBT Test: Parallel background tasks
SPDD Display modified DDIC objects
SPH1 Create and maintain telephony server
SPH2 Maintain outgoing number change
SPH3 Maintain incoming number change
SPH4 Activ./deactiv. telephony in system
SPH5 Define address data areas
SPH6 Server description is lang.-dep.
SPH7 Addr.data area texts are lang.-dep.
SPHA Telephony administration
SPHC Customizing telephone integration
SPR1 Delta Customizing for Project
SPR2 Delta Customizing for Enterprise IMG
SPR3 Upgrade Customizing for Project
SPR4 Upgrade Cust. for Enterprise IMG
SPR5 Transport enterprise IMG
SPR6 Transport Project: Status/Hdr.data
SPR7 Transport: Project notes
SPR8 Print WinWord IMG notes
SPR9 Display Structure: System install.
SPRA Display structure: Ext. Refer. IMG
SPRB IMG note editor switch
SPRM Update settings
SPRO Initial screen: Customizing
SPRP Project Management
SPRQ Start of a transaction
Tuning Transactions
ST01 System Trace
ST02 Setups/Tune Buffers
ST03 Performance, SAP Statistics, Workload
ST04 Select activity of the databases
ST05 SQL Trace
ST06 Operating System Monitor
ST07 Application monitor
ST08 Network Monitor
ST09 Network Alert Monitor
ST10 Table Call Statistics
ST11 Display Developer Traces
ST12 Application Monitor
ST14 Application Analysis
ST22 ABAP/4 Runtime Error Analysis
ST62 Create industry short texts
STAT Local transaction statistics
STDR TADIR consistency check
STMS Transport Management System
STP4 Select DB activity
STPC Test Workbench, Start test package
STTO Test Organization
STUN Menu Performance Monitor
STVR WB: Transport Utility R/3 –> R/2
User Maintenance Transactions
SU01 Maintain User
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 Mass Changes to User Master Records
SU12 Mass Changes to User Master Records
SU20 Maintain Authorization Fields
SU21 Maintain Authorization Objects
SU22 Auth. Object Usage in Transactions
SU23 Load Tables in TAUTL
SU24 Auth. obj. check under transactions
SU25 Copy initial defaults
SU30 Overall Authorization Checks
SU50 Maintain User Defaults
SU51 Maintain User Address
SU52 Maintain User Parameters
SU53 Display Check Values (Authorization values)
SU54 Maintain User Menu
SU55 Start User Menu
SU56 Analyze User Buffer
SU80 Archive user change documents
SU81 Archive user password change doc.
SU82 Archive profile documents
SU83 Archive authorization docs.
SU84 Read archived user change documents
SU85 Read archived password change doc.
SU86 Read profile change documents
SU87 Read authorization change documents
SU96 Table maint.: Change SUKRIA
SU97 Table maint.: Display SUKRIA
SU98 Call report RSUSR008
SU99 Call report RSUSR008
SUB Internal call: Submit via command fld
SUCH Translatability Checks
SUCU Table authorizations: Customizing
SUIM User Information System. All about user reports/info.
Others
FB03 To see the FI documents, see archiving.
FILE Archiving Path.
MB61 Material Documents
FCG Authorizations.
SF01 Give a logic name to a file.
SSCR Software changing registration.
VF03 Invoice documents
ZB12 Screen refresh.
OAM1 Optical archiving mirroring SPOV Print Request Overview