Important SAP Security Notes

Collective Security Note: 1394093

1394100 Access to RFC-enabled modules via SOAP

1375125 Report BEFG_TEMPLATE_CREATE must not be used in production

1363371 FS-CD: Missing authorization checks SAPRGEN_CD

1362972 Industry Solution Migration Workbench: Authorization check

1361038 Report RJ-JXINI generates unnecessary source code

1357370 No authorization check for editor

1356215 Missing authorization check in EMMACLS generation program

1355614 IS-M/ PMD: Obsolete source code in master data generator

1237762 ABAP systems: Protection against password hash attacks

821875 Security settings in the message server

2383 – Documentation: description of “super user” SAP*

2467 – Password rules and preventing incorrect logons

13202 – Security aspects in ABAP programming

26909 – SE16 – Security

68048 – Deactivating the automatic SAP* user

862989 – New password rules as of SAP NetWeaver 2004s (NW ABAP 7.0)

874738 – New password hash calculation procedure (code version E)

991968 – Value list for login/password_hash_algorithm

1023437 – ABAP syst: Downwardly incompatible passwords (since NW2004s)

1133739 – Security note: Security gap in Data Browser (SE16)

1392352 Cross-site scripting

1388864 ABAP web services authorization check does not work

1388729 SE80 authorization check in RS_TOOL_ACCESS

1375125 Report BEFG_TEMPLATE_CREATE must not be used in production

1363371 FS-CD: Missing authorization checks SAPRGEN_CD

1362972 Industry Solution Migration Workbench: Authorization check

1361038 Report RJ-JXINI generates unnecessary source code

1357370 No authorization check for editor

1356215 Missing authorization check in EMMACLS generation program

1355614 IS-M/ PMD: Obsolete source code in master data generator

1342183 Security information: Transaction FIAAHELP

1340457 Encoding fix for technical hidden fields

1339620 Cross Site Scripting (XSS) in cFolders

1339326 F&R: Remove hardcoded user name branches in code (security)

1336947 Security correction: Username hard coded

1335926 Some Fields are susceptible to Cross-site scripting

1335103 Security correction: removal of hardcoded user names

1334396 Security Checks: Removal of hardcoded user names

1334244 Some Fields are susceptible to Cross-site scripting.

1333668 Security Checks: Model Mix Planning

1330776 Files transferrable to EPS inbox w/o auth.

1329090 Deactivate parameter sap-wd-ssrConsole

1327917 Authorizatn check for transactions FPSEC1/FPSEC2/FPSEC3

1315883 RSUSR003: Standard passwords for hash code versions H and I

1306604 /SAPAPO/MC62 authorization for creating CVCs

1304803 Security note: Changing a transport without authorization

1302928 Field Level Authorizations Not Being Checked in CASE

1298160 Security note: Forbidden program execution possible

1294675 Location: Authorization Check for Planning Version

1294431 Anchor links are generated with unwanted HTTP href address

1292875 Cross Site Scripting (XSS) in cFolders

1287570 BBP_QUOT: Cross-Site Scripting ( XSS )

1275278 Security: HTML Encoding missing over the inputField tooltip

1271688 Security: Authorization check for technical help

1267878 Cross-site scripting error in BBP_POC

1262016 Authorization check for deleting CVCs (/SAPAPO/MC62) 2.

1261319 Help Center user name in the URL

1259881 Prevent “Webadmin” task from system admin

1259414 Cross Site Scripting:PCUI Stored JavaScript Vulnerability

1243004 Security Note: Missing SYSLOG entries for ABAP Debugging

1235367 Authorization check for deleting CVCs (/SAPAPO/MC62)

1232490 Authorization check SE80 for where-used list

1168813 Program DISPLAY_FUNC_INCLUDE

1167258 Program RS_REPAIR_SOURCE

1159009 RSDB2CMD switched to RSBDCOS0

1158063 P18:Security Note:RSSM_EXEC_COMMAND converted to RSBDCOS0

1151557 External theme root not html escaped

1146690 Passwords in SLD ABAP API

1143177 Cache settings incorrect for WebDynpro ABAP

1142067 Missing authorization check for hidden functions

1136823 SOBJ: Display of object directory permits changes

1136770 Security note: ICF system login

1133739 Security note: Security gap in Data Browser (SE16)

1120760 Security note: Missing authorization check for Web services

1115699 CO-OM Tools: SE16N: Adapting to SE16

1085326 Security Note: Check for ‘System -> Status’ (SE80)

1058531 BBPSC: Cross-site scripting error

0957038 Security gap in cross-site scripting

863362 Security checks in the SAP Early Watch Alert

Security Tip: Use RSECNOTE for Automatic checks for security notes, check SAP Note: 888889

Important SAP Notes on CCMS Monitoring

042692 Test tool for RFC links: sapinfo
The RFC connection test provided in transaction SM59 is either not available or does not provide enough information. Use the test tool sapinfo described in this SAP Note for testing.

135503 CCMS Monitoring Architecture: Meaning of profile parameters
The profile parameters of the monitoring architecture are explained in this SAP Note. These are: alert/MONI_SEGM_SIZE, alert/MTTREE, alert/ALERTS, and alert/PERFHIST.

202591 CCMS Monitoring Kernel Patches (composite SAP Note)
This SAP Note describes the changes to the monitoring architecture through the various patch collections.

209834 CCMS agent technology (composite SAP Note)
This SAP Note contains, in addition to basic information about the CCMS agents, known problems that can occur in connection with the CCMS agents, and their solutions.

212876 The new archiving tool SAPCAR
This SAP Note explains the operation of the archiving tool SAPCAR, with which the SAP Service Marketplace files are compressed.

308061 CCMS monitoring architecture: monitor 3x systems
The CCMS monitoring architecture is available as of SAP Basis 4.0B. However, you can also monitor systems as of SAP Basis 3.0D using the monitoring architecture. This SAP Note explains the procedure required to do this.

322075 Installing the CCMS agent sapccm4x fails
This SAP Note shows how you can solve a possible problem (error during the interaction of the semaphores between the agent and the application server) during the installation of the CCMS agent SAPCCM4X on application servers up to SAP Basis 4.6C.

371023 OS07/ST06: Monitoring of operating system data
Operating system data of (any) server is to be collected with the operating system collector SAPOSCOL and reported in the CCMS monitoring architecture or displayed in transactions ST06/OS07. This SAP Note describes the prerequisites for this.

420213 Composite SAP Note: Central monitoring of mySAP.com components
This SAP Note provides current information about monitoring mySAP.com components that are not described in the standard documentation (see SAP Service Marketplace and SAP Library [page 109]).

429265 CCMS monitoring architecture: Central auto-reaction
As of SAP Web AS 6.10, you can define central auto-reaction methods in the monitoring architecture in the context of the central monitoring of mySAP.com components. The auto-reaction methods are not started in the system, in which the alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location. This SAP Note describes the prerequisites for this scenario.

498179 Enable Monitoring of InQMy/SAP J2EE Engine
You want to include the SAP J2EE Engine in the CCMS monitoring architecture. This SAP Note shows how you can do this with the SAPCCMSR agent.

502461 CRM: CCMS agent PlugIn for IPC
You want to include the IPC Server component in the CCMS monitoring architecture. This SAP Note shows how you can do this with the SAPCCMSR agent and the appropriate PlugIn.

535199 CCMS agents: Monitoring log files
In the context of monitoring systems and system landscapes, you can use CCMS agents to monitor log files; that is, to search through certain files for one or more word patterns. If a search pattern is found, the monitoring architecture displays a message or an alert. This SAP Note explains the configuration required to do this.

516181 SAP Expert Monitor for EMC (SEME)
You want to monitor cached disk subsystems, such as EMC Disc Arrays (Symmetrix) with the monitoring architecture. This SAP Note shows how you can do this with the SAPCCMSR agent and the appropriate PlugIn.

522453 RZ20: Monitoring operating system data
This SAP Note describes how you can configure the collection of operating system data in the monitoring architecture.

584136 CCMS agents and kernels: Patches 2003 (composite SAP Note)
This SAP Note describes the changes to the monitoring architecture through the patch collections during 2003.

694057 CCMS agents and kernels: Patches 2004 (composite SAP Note)
This SAP Note describes the changes to the CCMS agents in the patch collections from 2004.

704349 Activating the CCMS monitoring for TREX
TREX can provide monitoring data for the CCMS using the agent technology. To do this, the CCMS agent SAPCCMSR and the operating system collector SAPOSCOL must be installed and configured on the TREX host. This SAP Note describes the steps on the TREX host.

730629 CCMS agents: Java interface for registration
You want to register the CCMS agent SAPCCMSR. The monitored object can be an instance of a J2EE Engine with a release status of SAP Web AS 6.20 or a host on which SAP standalone components/non-SAP components (such as a database) are running.
During the registration of the agent, you must enter a large amount of information about the CEN, the connection to it, and, if appropriate, the monitored J2EE instance. This SAP Note contains, as an attachment, a Java tool to simplify the registration.

734247 Registering CCMS agents for SAP Web AS Java as of 6.30
You want to register the CCMS agent SAPCCMSR, to centrally monitor an instance of a J2EE Engine as of SAP Web AS 6.30 using a central monitoring system (CEN) as of SAP Web AS 6.40 SP 1. During the registration of the agent, you must enter a large amount of data about the CEN, the connection to it, and the monitored J2EE instance. This SAP Note contains, as an attachment, a Java tool to simplify the registration.

809007 CCMS Agents and Kernel: Patches 2005
This SAP Note describes the changes to the monitoring architecture through the patch collections during 2005.

817714 Agent registration not possible with visual administrator
This SAP Note describes the manual installation of CCMS agents for a SAP NetWeaver J2EE instance or an ABAP+J2EE instance (double-stack) if it is not possible to perform the agent registration from the Visual Administrator.

902460 CCMS: Agent displays no J2EE data in RZ20
A SAPCCMSR CCMS agent has been installed for an SAP NetWeaver 2004s (7.00) J2EE instance and registered with a central monitoring system. The CCMS agent is displayed as ONLINE in transaction RZ21, and provides data for OS monitoring and log file monitoring. However, no monitoring data is displayed for the J2EE Engine.

914721 CCMS Agents and Kernel: Patches 2006
This SAP Note describes the changes to the monitoring architecture through the patch collections during 2006.

929635 “CCMS Agent Configuration” tab page is missing
Automatic registration of the CCMS agent from the Visual Administrator is not possible, since the CCMS Agent Configuration tab page in the Monitoring service of the dispatcher is not displayed. This problem can occur with the following release statuses:
􀂃 SAP NetWeaver 04 SP Stack 13 up to SP Stack 16
􀂃 SAP NetWeaver 2004s up to SP Stack 7

SAP Notes for Security

SAP Note 2467
Password rules & preventing unauthorized logons

SAP Note 4326
No user with super user authorizations

SAP Note 37724
Customer exits in SAP logon

SAP Note 40689
New reports for the User Information System

SAP Note 68048
Deactivating the automatic user SAP*

SAP Note 103019
SAPshortcut: Program parameter

SAP Note 142724
Prevention of multiple dialog logons

SAP Note 177895
Refitting the mySAP.com Single Sign-On capability

SAP on DB2 for Linux, UNIX and Windows: Important SAP Notes

DB2 9.5
DB6: Migration to Version 9.5 of DB2
1079000
DB6: Using DB2 9.5 with SAP Software
1089578
DB6: DB2 9.5 Standard Parameter Settings
1086130
DB6: Known Errors and available Fixes in DB2 9.5 LUW
1147821
DB6: Installations of Fix Packs for DB2 V9.5 (UNIX+Linux)
1138549
DB6: Installations of Fix Packs for DB2 V9.5 (Windows)
1138550

DB2 9
DB6: Migration to Version 9 of DB2
938522
DB6: Using DB2 9 with SAP Software
930487
DB6: DB2 9 Standard Parameter Settings
899322
DB6: Known Errors and available Fixes in DB2 9 LUW
977845
DB6: Installing FixPaks for DB2 9 (UNIX+Linux)
978554
DB6: Installing FixPaks for DB2 9 (Windows)
978555

DB2 UDB 8
DB6: DB2 UDB ESE Version 8 Standard Parameter Settings
584952
DB6: Migration to DB2 UDB Version 8
553963
DB6: Known Errors and available Fixes in DB2 UDB V8
609384
DB6: Installing V8.2 FixPaks (as of FixPak 9) on UNIX
603972
DB6: Installing V8.2 FixPaks (as of FP9) on Win NT/Win 2000
603981
DB6: Installing V8.2 Full Install with FixPak 9 (UNIX)
863620
DB6: Installing V8.2 Full Install with FixPak 9 (Windows)
863813

Support
DB6: Collect Stack Traces of DB2 Processes
932918
DB6: db2look: DDL and statistics information
102200
DB6: DB2 CLI trace
486951
DB6:Support for customers using DB2 UDB
686501
How to ensure support for DB2 after the end-of-service date
677786
DB2 UDB for UNIX and Windows: Collecting support data
83819
DB2-Explain with db2exfmt
156829

Installation/System Copy
DB6: SAP NetWeaver 2004s SR1 - Installation on Windows
919651
Inst. SAP NetWeaver 2004s SR1 on UNIX
921593
Hom./Het.System Copy SAP NetWeaver 2004s SR1
926085
DB6: SAP System Inst. with EXT Kernel on UNIX
928727
DB6: SAP System Inst. with EXT Kernel on Windows
928728
DB6: 6.20/6.40 Patch Collection Inst. - UNIX
967556
DB6: 6.20/6.40 Patch Collection Inst. - Windows
967555
6.40 Patch Collection Hom./Het.System Copy ABAP
971646
6.40 Patch Collection Hom./Het.System Copy Java
971645
DB6: Additional information on system copy with DB resources
713524

CCMS
DB6: Using DB2 9 automatic REORG
975352
DB6: Adjustments in EXPLAIN for DB2 Version 9
919763
DB6: Configuration of the planning calendar for AutoRunstats
860724
DB6: Adjustments in DBA Cockpit for DB2, Version 8, FixPak 9
825276
DB6: Incorrect values for STMM parameters in ST04 (DB2 9)
976285
DB6: New tables remain VOLATILE for AutoRunstats
966970
DB6: Incorrect evaluation of the F6 formula with REORGCHK
904465
DB6: 'Runtime' parameter doesn't work during DB13 Auto Reorg
858656
DB6: Activating row compression in the BW environment
937377
DB6: Backup jobs for remote databases
931122
DB6: AutoReorg cannot reorganize individual indexes
882928
DB6: Detailierte Deadlock Analyse ab DB2 UDB Version 8 FP 9
860212
DB6: Collecting Data for a Detailed Deadlock Analysis
837115
DB6: Extended deadlock monitor (individual shipment)
851220
DB6: REOPT and Hints in the EXPLAIN
876321
DB6: REORG options for LONG/LOB data
873424
DB6: Offline backup ends with job error (DB13)
427982
DB6: Incorrectly cataloged table functions
978319
DB6: Unprecise Table and Index Sizes in Transaction DB02
701546
DB6: Resetting DB13 scheduling
642345
DB6: Troubleshooting for logical commands
549303
DB6: Maintaining table statistics via transaction DB13
434495
DB6: Reorganizing tables via transaction DB13
431430
DB6: Database restore requires additional tape
1175050

Admin Tools
Central SAP Note for DB6 Admin Tools
538315
DB6: Installing the Latest 4.6D DB2 Admin Tools
410252
DB6: Installing the Latest 6NN DB2 Admin Tools
455506
DB6: Archiving log files with DB2 log file management
913481
DB2 UDB: postprocessing DCK kernel for COM releases
350783
DB6: brdb6brt -Installing the latest redirected restore tool
511323
DB2 UDB for UNIX / NT: User exit: Description / RCs
104019
DB6: Admin Tools and Split Mirror
594301
DB6: Database restore requires additional tape
1175050

BW/BI
Setting basis parameters for BW Systems
192658
DB6: DB2 UDB - BW Performance - Overview of notes
374502
DB6:Administration & Performance on SAP BW, SAP SCM, SAP SEM
546262
DB6: Multi-Dimensional Clustering for SAP BW 3.x
942909

Miscellaneous
DB6: Supported Fix Packs for DB2 UDB for UNIX and Windows (contains end-of-service dates for DB2 Releases)
101809
DB6: Table conversion using DB6CONV
362325
FAQs: DB2/UDB tablespace
543897
mysap.com software on DB2 UDB on 64-bit FAQ
395975
DB6: Tips and tricks for creating DB2 tablespaces
147634
DB6: Move tables to other DB2 tablespaces
136702
DB6: Online help with DB2 CLP/documentation
73042
DB6: Database multiconnect with EXEC SQL
200164
DB6: R3load migration accelerated with CLI LOAD API
454173
DB6: WEB sites containing related information
690471
DB6: DBSL trace for performance/error analysis
31707

MaxDB - Important SAP Notes

767598
Available Documentation
820824
FAQ: MaxDB/ SAP liveCache Technology
846890
FAQ: MaxDB Administration
819641
FAQ: MaxDB Performance
819324
FAQ: MaxDB SQL Optimization
990602
FAQ: CCMS for MaxDB and SAP liveCache Technology
822239
FAQ: MaxDB Interfaces
826037
FAQ: MaxDB Support
1007129
FAQ: DB Migration with MaxDB as Target

Notes on SAP License

094998 - Request license key for systems / delete systems

767123 - NetWeaver 04 License Key

765620 - SAP NetWeaver Developer Studio

0566263 - SAP license in upgrade to Release 6.x (or higher)

0628630 - Core dump in SlicShmInit

0174911 - Formation of the hardware key (customer key)

0612645 - Performance problems accessing table LICENSE

0432308 - SAPLICENSE 6.10: new field SYSTEM-NR

0355536 - Importing the SAP license from a file

0538081 - High availability SAPLICENSE

0576136 - License expiry date is not displayed correctly

0428966 - Transaction SLICENSE: installation is not working

0485233 - Table MLICHECK in wrong table space on Oracle

742024 - Downloading the license key

181543 - License key for high availability environment

198140 - Reassigning systems

Data Archiving - Requirements & Importing Archving Technology

The main purpose of data archiving is to remove from the database application data that is no longer needed in day-to-day business, with the aim of using resources more efficiently. The following requirements must be taken into account when archiving data:

• Legal requirements: Some kinds of data must be archived so that they can be analyzed at any time in the future, for example data required by the tax authorities. These requirements are subject to the laws of the relevant country. SAP has developed the Data Retention Tool (DART) to enable the US Internal Revenue Service to analyze archived data. The tool includes functions for creating transparent files from archived data and to display this data.

• Technical requirements: From a technical point of view, the question is whether data can still be read long after it has been archived, independent of the hardware used at the time of archiving and the software release status. To guarantee this, SAP Data Archiving stores, together with the actual application data, additional information about the hardware that was used to write the data to the archive and what type of data structure was applied.

• Business requirements: From the business point of view, only those data objects that are no longer required in day-to-day operations may be removed from the database. Therefore, a logic check must be performed to ensure that only data objects belonging to completed business processes can be archived. The high level of integration between R/3 System applications means that the data objects are closely linked. Consequently, it is essential, during archiving, to check whether the removal of a specific data object from the database requires other objects to be archived at the same time.

Important Archiving Terminology

Reorganization

This term has a double meaning in the SAP context. Firstly, it refers to the physical deletion of application data from the database. Secondly, - the true meaning - refers to the reorganization of the database.

In the database, individual table lines containing datasets are stored in database blocks. Deleting, changing and creating datasets creates gaps in the blocks. These gaps can no longer be used. Fragmentation of the database can, in some circumstances, increase the time needed by the system to search for table contents.

Removing the effects of this fragmentation by closing the gaps and thereby enabling more efficient use of the available memory space is what is meant by the term (database) reorganization. This process entails the physical relocation of data from a logical database segment to a contextually-related area in the memory.

Optical archiving

Optical archiving refers generally to the electronic storage and management of documents in storage systems beyond the R/3 System. In most cases, data is stored in optical media such as CDs or WORMs;hence the designation "optical archiving". The term is, however, confusing, and it would be preferable to refer to "imaging" or "electronic data storage" since the term "optical archiving" only describes the physical storage. In principle, all media - and not just optical storage media - can be used that are supported by the storage system that is connected to the SAP System.

Documents that can be stored in this way include

Scanned original documents such as suppliers' invoices

Outgoing documents, such as invoices that are created electronically in R/3 and then forwarded

Print lists created in R/3

In these cases, the documents created are not stored in the R/3 database, but are transferred to document storage systems. The SAP System only maintains links to the externally stored document, thereby enabling access. Documents that are stored (not archived) in this way can be displayed in R/3, but cannot be reloaded into the database. This is due to the different formats in which documents and applications are saved. Whilst application data is stored in the database in a structured format (CI, coded information), scanned documents are stored in NCI format (non-coded information), which cannot be interpreted by the applications.

SAP ArchiveLink

SAP ArchiveLink is an interface that is integrated into the SAP Basis component. It controls communication with storage systems. This standard interface enables access to documents created in SAP applications and stored in a storage system. The storage system must be correctly configured and connected to the R/3 System.

Backup and Restore

Backup refers to the (saved) copy of the database contents that serves as a precaution against data loss. This enables the reinstatement of the database as it was before the system failure. Restore refers to the rewriting of the contents of the backup copy in an emergency.

The following defines more precisely the term Data Archiving:

"Data Archiving is the consistent removal of data objects from the database. This involves writing all table entries that define a data object in archive files outside the database. Consistency of business data is ensured by the SAP archiving programs, which remove all the relevant table entries."

Copying Tables Entries Between Two Different Systems

There are several ways to copy table entries between two different SAP systems. One of the most efficient is by using the R3trans utility. The tp program could also be used; however, the transport control program tp performs many additional checks and imposes some restrictions on the table types to be transported.

For example, assume that, after a client copy between two SAP systems, a table content could not be completely copied to the target system (import phase) because the table reached the maximum number of extents in the underlying database. You can avoid having to perform a whole import again by transporting a single table with R3trans.

The general procedure to do this is as follows:
1. Create the control file for the export
2. Run the control file in the source system
3. Check the export log
4. Create the import control file in the target system
5. Run the import control file in the target system
6. Check the import log and the data in the target system


Detailed Procedure


After verifying the client copy log, due to some storage problems in table MOFF, this table could not be completely copied. To avoid having to perform the whole client copy process, just the entries on table MOFF from the source client will be copied to the table MOFF on the target client 010 in the target system T12.

1) In the source system (C12), create a control file, for example, expmoff.ctrl with the following content:
export
client=002
select * from moff where mandt = '002'

2) Run the R3trans utility with the previous control file: R3trans −w expmoff.log −u 18 expmoff.ctrl. While the −w flag indicates the log file, the −u flag sets unconditional modes for the transport. In the export phase, unconditional mode 1 indicates the system to ignore the wrong status of transport requests. Mode 8 allows direct selection of tables when the default modes are not allowed.
By default, the previous command generates the data file trans.dat in the directory where the export has been executed. If both source and target systems share the transport directory, it won't be necessary to copy the trans.dat file. Otherwise, you must use available tools for file transfer, for example, ftp.

3) Check the export log file, expmoff.log, and verify it did not contain any errors.

4) Once in the target system, create the import control file, for example, impmoff.ctrl, with the following content:

import
client=010

5) Then execute it with the R3trans tool: R3trans −w impmoff.log −u 248 impmoff.ctrl
By default it uses the data file trans.dat generated by the previous command file.
The unconditional modes used in the import phase are: 2 for enabling the overwriting of the original, 4 which ignores that the transport request was intended for a different target system, and 8 which allows for importing tables which are restricted by their table types.
If you use the default options for the import, you do not need a control file. The import can be
performed directly with R3trans −i .

6) Check the import log file, impmoff.log, to check that the import runs fine without errors. You can also log on to the target client, 010, in the target system and look up the table contents with standard dictionary utilities, such as the data browser (transaction code SE16).

Important SAP Tcodes

ABAP & Tables Related Transactions
SA38 To execute a Abap program
SE38 ABAP Editor
SE11 ABAP/4 Dictionary Maintenance
SE80 ABAP Development Work Bench
SE16N General Table view ( very Useful)
SE16 Data Browser or table viewer

Administration
AL11 Display SAP Directories
BD54 Maintain Logical System
OSS1 Logon to Online Service System
SALE IMG Application Link Enabling(ALE)
SARA System Archive Administration
SCU0 Customizing Cross-System Viewer
SICK Installation Check (System Initial Consistency Check)
SM01 Lock/unlock Transactions
SM02 Send System Messages to all users
SM04 List of Users logged into the Client
SM12 Display and Delete Locks
SM13 Display Update Request Records
SM14 Update Program Administration
SM21 System Log
SM35 Batch Input Overview
SM50 Work Process Overview
SM51 SAP Servers list
SM56 Number Range Buffer
SM58 Transactional RFC overview
SM59 Display and Maintain RFC Destinations
SM66 Global Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Support Package Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
ST22 ABAP/4 Runtime Errors
SU56 User Buffers
SMT1 Maintain or display Trusted systems



Client Administration commands
SCC3 Client Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SCC1 Client Copy by transport request


Configuration
FILE Cross-Client File Names/Paths
RZ04 Maintain Operation Modes and Instances
RZ10 Maintenance of Profile Parameters
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SWU3 Automatic Workflow Customizing
SPRO Customizing: Execute project
SM63 Display/Maintain Operating Mode Set


Database Administration
DB01 Analyze exclusive lockwaits (database snapshot)
DB02 Analyze tables and indexes (Space History overview)
DB03 Configuration Parameter Changes
DB12 DB Backup and Recovery Monitor
DB13 DBA Planning Calendar
DB15 Tables and archiving objects


Background Jobs
SM36 Define or schedule a Background Job
SM37 Background Job Overview & Maintenance
SM49 Execute External Operating System commands
SM62 Display or maintain Events
SM64 Trigger Event in backgroung processing
SM65 Background Processing Analysis Tool (testing)
SM69 Display or Maintain External OS Commands


Monitoring
AL04 Sap Performance Monitor
AL16 Operating System Monitor
RZ20 CCMS Monitoring
AL08 Current Active Users
OS01 LAN check by ping
RZ01 Job Scheduling Monitor (external program)
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST03 Performance, SAP Statistics and Workload analysis
ST03n Work load Analysis
ST04 Performance: Database snapshot
ST05 Performance Analysis
ST06 Operating System Monitor
ST07 Application monitor : User distribution
ST10 Table call statistics
STAT Local transaction statistics

Spool
SP01 Output Controller
SP02 List of the users spool requests
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration (defining printers etc…)

Transports
SE01 Transport Organizer
SE06 Set Up Workbench Organizer (Post-installation actions for transport organizer)
SE07 CTS Status Display (import monitor)
SE09 Workbench request Organizer
SE10 Customizing request Organizer
STMS Transport Management System
SM30 Table View Maintenance
SM31 Table Maintenance

User Administration
PFCG Profile Generator (Activity Group Maintenance)
SU01 User Maintenance (single user maintenance)
SU01D User Display (safe)
SU02 Maintain Authorization Profiles (depreciated)
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance (You cannot change user master data using this)
PFUD User Master Data Reconciliation
SMLG Maintain Logon Group
SUPC Mass generation of Profiles for activity groups
SUIM User Information system (very good transaction code)
One can find any information about a user using this t-code


Central User Administration
SCUA Activate/maintain CUA
SCUG Transfer user
SCUL Central User Management Log Transaction used to view CUA audit and error logs.

Related to Idocs
WEDI IDoc and EDI Basis
WE02 IDoc list display
WE07 IDoc statistics
WE46 IDoc administration

Other Transactions
HIER Internal Application Component Hierarchy Maintenance
WE20 Maintain Partner profiles
WE21 Port definition
WE47 Status Maintenance