RTERM SAP (Internal Structure) Structure details
Description: Internal Structure
Structure field list including key, data, relationships and ABAP select examples
RTERM 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 "Internal Structure" 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_RTERM TYPE RTERM.
The RTERM table consists of various fields, each holding specific information or linking keys about Internal Structure data available in SAP. These include BEGRIFF (Term in terminology database), QUELLSPR (Language Key), ZIELSPR (Language Key), PFAD (Path).. 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. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP RTERM structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| APPLSTAMM | Application master record | TERMASTAMM | CHAR | 60 | TERMASTAMM | ||||
| BEGRIFF | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| QUELLSPR | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| ZIELSPR | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| PFAD | Path | TERMPFAD | CHAR | 60 | TERMPFAD | ||||
| QUELLBEGR | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| ZIELBEGR | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| FILE | File name | TERMFILE | CHAR | 60 | TERMBEGR | ||||
| BEREICH | Print filter | TERMBER | CHAR | 35 | Assigned to domain | TERMBER | |||
| FUNCT1 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT2 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT3 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT4 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT5 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT6 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT8 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| FUNCT9 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| DATUM | Date | DATUM | DATS | 8 | DATUM | ||||
| VONBEGR | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BISBEGR | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| FUNCT7 | Short text | FUNCTION_D | CHAR | 1 | FUNCTION | ||||
| AENDERER | User Name | UNAME | CHAR | 12 | UNAME | ||||
| BAENDERER | User Name | UNAME | CHAR | 12 | UNAME | ||||
| GLOSSAR | Glossary entry | TERMGLOS | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF1 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF2 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF3 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF4 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF5 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF6 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF7 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| BEGRIFF8 | Term in terminology database | TERMBEGR | CHAR | 60 | TERMBEGR | ||||
| SUCHSPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| ANLEGER | Entered by | TERMANLEG | CHAR | 12 | UNAME | ||||
| LAENDERER | Changed by | TERMAENDER | CHAR | 12 | UNAME | ||||
| ANLEGDAT | Entered on | TERMANLDAT | DATS | 8 | DATUM | ||||
| AENDERDAT | Last changed on | TERMAENDAT | DATS | 8 | DATUM | ||||
| GENUS | Gender | TERMGEN | CHAR | 1 | TERMGEN | ||||
| KATEGORIE | Part of speech | TERMKAT | CHAR | 1 | TERMKAT | ||||
| STATUS | Entry status | TERMSTAT | CHAR | 1 | TERMSTAT | ||||
| ALLLANGU | All languages | ALLLANGU | CHAR | 60 | TEXT60 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RTERM using ABAP code?
As RTERM 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 RTERM as there is no data to select.How to access SAP table RTERM
Within an ECC or HANA version of SAP you can also view further information about RTERM and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects