SAP T Code

SAP transaction codes, known as T-codes, are the operational language of every SAP environment. These four-character shortcuts give users, administrators, and developers direct access to any function within an SAP system, from processing daily business transactions to managing authorizations and running ABAP programs. As organizations migrate to SAP S/4HANA and SAP Fiori replaces the SAP GUI, understanding which T-codes carry forward, which are replaced, and how T-code-based security models must evolve has become a central concern for SAP professionals navigating the path to the intelligent enterprise.

What Are SAP T-Codes?

An SAP T-code is a four-character shortcut entered in the SAP command field to launch a specific transaction directly, bypassing menus entirely. T-codes span every functional area: user administration (SU01), role management (PFCG), ABAP development (SE38), table browsing (SE16), and system configuration (SPRO), among thousands of others. Users build favorites lists for the codes they access most. Administrators rely on T-codes to manage authorizations and monitor landscapes. With the transition to SAP S/4HANA, SAP simplified its T-code inventory, retiring or replacing codes tied to ECC-era data models, making T-code assessment a required step in migration planning.

SAP transaction codes, known as T-codes, are the operational language of every SAP environment. These four-character shortcuts give users, administrators, and developers direct access to any function within an SAP system, from processing daily business transactions to managing authorizations and running ABAP programs. As organizations migrate to SAP S/4HANA and SAP Fiori replaces the SAP GUI, understanding which T-codes carry forward, which are replaced, and how T-code-based security models must evolve has become a central concern for SAP professionals navigating the path to the intelligent enterprise.

What Are SAP T-Codes?

An SAP T-code is a four-character shortcut entered in the SAP command field to launch a specific transaction directly, bypassing menus entirely. T-codes span every functional area: user administration (SU01), role management (PFCG), ABAP development (SE38), table browsing (SE16), and system configuration (SPRO), among thousands of others. Users build favorites lists for the codes they access most. Administrators rely on T-codes to manage authorizations and monitor landscapes. With the transition to SAP S/4HANA, SAP simplified its T-code inventory, retiring or replacing codes tied to ECC-era data models, making T-code assessment a required step in migration planning.

What Use Cases Are Referenced?

Identifying Deleted and Replaced T-Codes for S/4HANA Migration Planning

A SAPinsider session by Arghadip Kar walks through how to identify which SAP ECC transaction codes have been deleted or replaced in SAP S/4HANA. The guidance helps organizations planning migration assess custom code and processes that rely on decommissioned T-codes, enabling more accurate scope and risk planning before go-live.

Mapping T-Codes to Common Phrases for Usability and Access Control

A SAPinsider article by Muhammad Ramzan details how to build an ABAP program that maps standard transaction codes to plain-language phrases, removing the burden of memorization for frequent users. The approach preserves all underlying authorization checks, ensuring that role-based access controls tied to the original T-codes remain fully enforced.

T-Code Security Model Redesign During a Greenfield S/4HANA Implementation

A SAPinsider case study of Versum Materials’ 15-month greenfield SAP S/4HANA implementation details how the company shifted from a T-code-based user security model to a role-based design. The transition required significant post-go-live remediation training, as users defaulted to requesting access via transaction code rather than by job function.

Managing SAP Fiori Authorizations Through T-Code PFCG

A SAPinsider article by Lisa Dodson and Alessandro Banzer explains that even as SAP Fiori replaces the SAP GUI, role administrators still manage Fiori authorizations through transaction code PFCG. The piece covers how PFCG roles are built for the frontend server, how catalog and group assignments work, and how backend authorization objects are maintained alongside Fiori app access.

T-Codes and Identity Governance in the SAP IDM Retirement Transition

A SAPinsider article covers how the retirement of SAP Identity Management in 2027 forces organizations to rethink how SAP authorization objects and transaction codes map into identity governance frameworks. As cross-system segregation-of-duties risk expands across SAP and non-SAP environments, T-code-level access controls must be governed within a unified, cross-application policy layer.

What SAPinsider Research Supports This Topic?

Cybersecurity Threats and Challenges to SAP Systems (2025)

SAPinsider’s 2025 cybersecurity benchmark study found that 92% of organizations consider their SAP systems mission-critical, yet only 34% have a mature cybersecurity posture. The findings underscore the risk exposure created when T-code-level access is not governed with the same rigor applied to infrastructure and network security.

Automating and Integrating GRC Processes (2024)

SAPinsider’s GRC benchmark research, based on a survey of 170 community members from March through June 2024, found that 51% of organizations use SAP GRC Access Control, the tool through which T-code-based segregation-of-duties risks are detected and remediated. The move to SAP S/4HANA was cited by 45% as the top driver of GRC strategy changes.

SAP S/4HANA Migration Benchmark Report (2025)

SAPinsider’s SAP S/4HANA Migration 2025 benchmark report, based on 170 community responses, found that 32% of organizations have completed their migration, with custom code assessment, including the review of T-code dependencies, among the top technical challenges cited by organizations still working through implementation.