SAP Basis Tables List: Complete Reference Guide to Every System Administration Table Every Basis Professional Must Know

🛠️ How to Find and Use SAP Basis Tables

Before diving into the SAP Basis Tables List, it is important to understand how to actually access and work with these tables inside an SAP system, and why Basis tables are treated more cautiously than functional ones.

Transaction SE11 - ABAP Dictionary

SE11 is the ABAP Data Dictionary. It is the primary tool for viewing a Basis table's metadata - structure, fields, data types, key fields, and technical settings such as delivery class and table category. Every Basis table in this list can be viewed in SE11. Simply enter the table name and press Display. The Application Component field on the technical settings tab will show BC or a BC sub-area for every genuine Basis table, which is the most reliable way to confirm a table belongs to this layer rather than a functional module.

Transaction SE16N - Table Browser

SE16N allows you to browse live data stored inside any Basis table. Enter the table name, apply filters on key fields, and execute to retrieve rows of data. This is the correct way to confirm a user's actual lock status in USR02, check a transport's real release status in E070, or see a background job's true status in TBTCO - all without relying purely on what the corresponding screen transaction displays. SE16N is read-only and cannot change data, making it safe for Basis-layer investigation.

Why Direct Table Maintenance Is Rare for Basis Tables

Unlike many functional tables, several Basis tables - particularly USR02 and the lock/enqueue tables - should essentially never be changed through direct SE16 table maintenance, even by an experienced administrator. Almost every legitimate change has a dedicated, supported transaction that correctly updates all related tables, writes the necessary audit trail, and triggers required system logic such as profile regeneration. Direct table edits bypass this logic and are one of the fastest ways to leave a system in an inconsistent state.

"Example: Select a user's logon data from USR02
SELECT SINGLE *
  FROM usr02
  INTO @ls_usr02
  WHERE bname = @lv_user_id.

👤 SAP User Administration Tables - USR Tables

Also SAP user administration is built on a small set of tightly related tables sitting behind transaction SU01. These tables store everything from logon credentials and password validity to general preferences and role assignments. USR02 and USR01 are the two most frequently referenced tables in any user-related investigation.

Core User Master Tables

The user master record is split across multiple tables, each storing a different category of data. USR02 holds logon-relevant and password data. USR01 holds general preferences. USR21 links the technical user name to the underlying person/address record. This split allows SAP to separate sensitive authentication data from everyday user preference settings.

Role and Authorization Assignment Tables

📦 SAP Transport Management Tables - E0 Tables

Transport management tables track every change request and task moved through the system landscape via the Change and Transport System (CTS). These tables sit behind transactions SE09 and SE10, and are the tables every Basis administrator checks first when a change appears to be missing in a target system.

⏱️ SAP Background Job Tables - TBTC Tables

Background job tables store every scheduled, running, completed, or failed batch job in the system, sitting behind transaction SM37. TBTCO and TBTCP are the two tables every Basis administrator queries when a nightly job appears not to have run correctly.

🖨️ SAP Spool and Output Management Tables - TSP Tables

Spool tables track every print and output request generated in the system, sitting behind transactions SP01 and SP02. TSP01 is the central reference table for confirming whether SAP successfully generated a given output, which is the first checkpoint when a user reports a missing printout.

🔒 SAP Lock, RFC, and System Monitoring Tables

This group covers three closely related but distinct Basis areas: the enqueue/lock mechanism behind SM12, RFC destination definitions behind SM59, and system event logging behind SM21 and ST22. Together these tables answer most "why can't I save," "why didn't the interface work," and "why did this crash" investigations.

Lock Management (Enqueue)

RFC Connectivity

System Logging and Runtime Errors

SAP Basis Configuration and Client Tables

Beyond user, transport, and job tables, SAP Basis also maintains a set of foundational configuration tables that describe the system landscape itself - clients, logical systems, and system-wide parameters. These are typically maintained via SCC4, SALE, and RZ10/RZ11 rather than direct table maintenance.

🔎 How to Find Any SAP Basis Table You Need

Even with this comprehensive SAP Basis Tables List, there will be times when you need to find a Basis table that is not covered here. SAP provides several built-in techniques to discover any table in the system without relying on documentation.

Method 1 - Filter DD02L by Application Component

Open SE16N on table DD02L, the dictionary's own master list of every table, and filter the Application Component column to BC (or a BC sub-node). This instantly isolates Basis-layer tables from the much larger set of functional module tables.

Method 2 - Prefix Wildcard Search

Many Basis tables follow recognisable prefixes: USR* for user data, E0* for transport objects, TBTC* for background jobs, TSP* for spool, and RFC* for RFC destinations. Entering one of these as a wildcard in SE16N's TABNAME filter on DD02L quickly surfaces every related table in that area.

Method 3 - F1 Technical Information on a Basis Screen

The fastest method for a specific field. In any Basis transaction (SU01, SM37, SP01, and others), place your cursor on a field and press F1, then click Technical Information. SAP displays the exact table and field name backing that screen element, exactly as it does for functional transactions.

"Use this ABAP snippet to find tables with a specific field, e.g. BNAME
SELECT tabname, fieldname, ddtext
  FROM dd03vv
  INTO TABLE @lt_fields
  WHERE fieldname = 'BNAME'
    AND   tabclass  = 'TRANSP'
  ORDER BY tabname.

Method 4 - Use the Supported Transaction First

Before browsing a Basis table directly, check whether a supported transaction already presents the same data more safely and with more context - SU01 for user data, SE09/SE10 for transports, SM37 for jobs, SP01 for spool, SM12 for locks, SM59 for RFC destinations. Direct table access is best reserved for cross-checking or investigating something the transaction screen does not show clearly.

📋 SAP Basis Tables List - Master Quick Reference

The table below is your single-page quick reference covering the most important Basis tables across every major system administration area. Bookmark this page and use it whenever you need to quickly identify which Basis table stores the data you are looking for.

📘 Related SAP Tutorials

🔗 Important Related Links