SAP STTEXT_PROJ Structure for multilang project definition Table data and field list

STTEXT_PROJ is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Structure for multilang project definition" Information within sap ABAP programs.

This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.

i.e. DATA: wa_STTEXT_PROJ TYPE STTEXT_PROJ.

The STTEXT_PROJ table consists of various fields, each holding specific information or linking keys about Structure for multilang project definition data available in SAP. These include DESCRIPTION (PS: Short description (1st text line))... 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. .

STTEXT_PROJ structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)

SAP STTEXT_PROJ structure 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 STTEXT_PROJ table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.

Key field

Non-key field

How do I retrieve data from SAP structure STTEXT_PROJ using ABAP code?

As STTEXT_PROJ is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on STTEXT_PROJ as there is no data to select.

How to access SAP table STTEXT_PROJ

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

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