An SAP transaction – what is that actually?
SAP transactions are programs or function modules that are called up within an SAP system by users or automated processes. It is the functional component of an SAP system, which is used to change data in the SAP database.
The transaction is controlled by the SAP system, not directly by the database. To avoid the simultaneous modification of data objects and thus inconsistencies due to parallel transactions, each transaction locks the data records to be modified for sole use
Important here: A transaction describes a whole series of SQL statements that are interpreted as a closed, overall unit: the LUW, or Logical Unit of Work.
If a transaction stops before the defined completion, the database rolls back – since the transaction that ended with errors could potentially not write the data completely correctly, the SAP system resets the data to the old state. This concept of transactions is intended to avoid logical errors and ensure consistent database states.
Transaction versus Transaction Code / T-Code
Transactions have short names called transaction codes (T-codes), which usually consist of uppercase letters and numbers.
The number of original transactions depends on the SAP modules used but is in the hundreds of thousands. In addition, users can define further, own transaction codes. Like almost all customer-specific changes in the SAP environment, these begin with the letter “Z”: Z programs, Z programs.
Calling transaction SE16N (Data Browser) with table TSTC displays the complete list of all transactions, depending on the parameterization.
The most important SAP standard transactions at a glance
There are various sites online that list all transaction codes with more or less detailed descriptions. From our point of view, the most important are the transactions of the basic administration, as also listed by the SCN :
system administration
– SU01 user administration
– SU01D user display
– SU02 maintain authorization profiles
– SU03 maintain authorizations
– SU05 maintain Internet users
– SU10 user mass maintenance
– SMLG maintain log on group
– SUPC profiles for activity groups
– SUIM information system authorizations
– PFCG profile generator
– PFUD user master data comparison
– S002 menu Simple system administration
– ZAUT application for new users, change of authorization, etc.
Tenant Management
– SCC3 Checking the log for client copies
– SCC4 Client management
– SCC5 Delete client
– SCC7 Post-processing of client import
– SCC8 Export client
– SCCL Local client copy
– SCC9 Remote client copy
Database Management
– DB01 Exclusive Lock Wait Times Analysis
– DB02 Table and Index Analysis
– DB12 DB Backup Monitor
– DB13 DBA Planning Calendar
– DB15 Data Archiving: Database Tables
– ST04 SQL Server Performance Analysis
Transportation Management System
– STMS Transport Management System
– SE01 Transport and Correction System
– SE06 Set Up Workbench Organizer
– SE07 CTS Status Display
– SE09 Workbench Organizer (Transport Release)
– SE10 Customizing Organizer
– SE11 ABAP/4 Dictionary Maintenance
– SE16 Data Browser
– SE80 Repository Browser
– SM31 Table maintenance
– SCC1 role transfer between clients
Management of background jobs
– SM36 define background job
– SM37 background job overview
– SM39 job analysis
– SM49 execute external operating system commands
– SM62 maintain events
– SM64 release an event
– SM65 analysis tool for background processing
– SM69 maintain external operating system commands
spool management
– SP01 output control
– SP11 TemSe directory
– SP12 TemSe administration
– SPAD spool administration
– AL11 display SAP directories
– BD54 maintain logical systems
– OSS1 logon to the online service system
– SALE IMG application link activation
– SARA archive administration
– SICK installation check
– SM14 Post program management
– SM35 batch input monitoring
– SM56 number range buffer
– SM58 asynchronous RFC error log
– SM59 RFC destinations (display/maintain)
– SAINT SAP add-on installation tool
– SPAM SAP Patch Manager
– SPDD display of modified DDIC objects
– ST11 display of developer traces
Daily monitoring TCodes
– SM04 User List
– AL08 Current Active Users
– SM12 Display and Delete Locks
– SM13 Display Update Records
– SM21 System Log
– SM50 Work Process Overview
– SM51 List of SAP Servers
– SM66 System-Wide Work Process Overview
– ST22 ABAP/4 Runtime Error Analysis
– ST01 System Trace
– ST02 Buffer Setup/Tune
– ST04 Select DB Activities (SQL Server Performance Analysis)
– ST05 Performance Trace
– ST06 or ST06N Operating System Monitor
– ST10 Table Call Statistics
– ST03 Performance, SAP Statistics, Workload
– SU56 Analyze User Buffers
– STAD user transaction analysis
– SM02 system message
Other monitoring transactions
– OS01 LAN check with ping
– RZ01 job scheduling monitor
– RZ03 presentation, control of SAP instances
– ST07 application monitor
– STAT local transaction statistics
Other helpful transactions in everyday life SAP
– AL22 display of dependent objects
– BAOV information on add-on version
– SA38 ABAP reporting
– SE38 ABAP editor
– HIER maintenance of the internal application component hierarchy
– ICON display of icons
– WEDI IDoc and EDI basis
– WE02 IDoc display
– WE07 IDoc -Statistics
– WE20 partner agreements
– WE21 port description
– WE46 IDoc management
– WE47 status maintenance
– $TAB refresh the table buffer
– $SYNC updates all buffers except the program buffer
Also, read more on related topics
Your contact at Firnkorn & Stortz on the subject of SAP transactions
Firnkorn + Stortz GmbH
Thomas Firnkorn