SAP TDA11 Allocation of OK-codes to the trans.codes Table data and field list

TDA11 is a standard SAP Pooled Table which is used to store Allocation of OK-codes to the trans.codes data in SAP systems, such as SAP R/3, S/4HANA, depending on the version and release level.

The TDA11 table consists of various fields, each holding specific information or linking keys about Allocation of OK-codes to the trans.codes data available in SAP. These include SANLF (3-Byte field), STATUS (3-Byte field), TCODE (Transaction Code)... See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .

TDA11 pooled table Technical Details:

Delivery Class: S - System table, maint. only by SAP, change = modification
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified


SAP TDA11 pooled table fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the TDA11 table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
OKCTransaction Code TCODECHAR20Assigned to domainTCODETCD
SANLF3-Byte field CHAR3CHAR3CHAR3
STATUS3-Byte field CHAR3CHAR3CHAR3
TCODETransaction Code TCODECHAR20TSTCTCODETCD

Key field Non-key field



How do I retrieve data from SAP table TDA11 using ABAP code

The following ABAP code Example will allow you to do a basic selection on TDA11 to SELECT all data from the table
DATA: WA_TDA11 TYPE TDA11.

SELECT SINGLE *
FROM TDA11
INTO CORRESPONDING FIELDS OF WA_TDA11
WHERE...

How to access SAP table TDA11

Within an ECC or HANA version of SAP you can also view further information about TDA11 and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).