DISOTXT SAP (SDB: Dialog Text for Solution) Structure details
Description: SDB: Dialog Text for Solution
Structure field list including key, data, relationships and ABAP select examples
DISOTXT 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 "SDB: Dialog Text for Solution" 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_DISOTXT TYPE DISOTXT.
The DISOTXT table consists of various fields, each holding specific information or linking keys about SDB: Dialog Text for Solution data available in SAP. These include CLIENT (Client), ISLNR (SDB: Solution Number), ISLVR (SDB: Solution Version Number), LANGU (Language Key).. 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: Not classified
SAP DISOTXT 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 |
| CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| ISLNR | SDB: Solution Number | ISLNR | CHAR | 12 | ISOL | ALPHA | ISLNR | ISLNR | |
| ISLVR | SDB: Solution Version Number | ISOVER | NUMC | 3 | Assigned to domain | ISOVER | ISLVR | ||
| LANGU | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| ISLTXT | SDB: Solution short text | ISLTEXT | CHAR | 40 | TEXT40 | ||||
| INDLTXT | Object Long Text Available | INDLTX | CHAR | 1 | CHAR1 | ||||
| TRSTAT | SDB: Translation Status for the text fields | TRSTAT | CHAR | 1 | CHAR1 | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERTIM | Time, at Which Record Was Added | ERZEIT | TIMS | 6 | UHRZT | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| AETIM | Time of Change | AEZEIT | TIMS | 6 | UHRZT | ||||
| FLGDEL | Delete Data Record | KZLOESCH | CHAR | 1 | CHAR1 | ||||
| ISLICON | SDB: Icon for solution Long Text | ISLICON | CHAR | 40 | SYCHAR40 | ||||
| ISLSEL | Selection | SELECT | CHAR | 1 | SELKZ | ||||
| FLGUPD | SDB: Indicator to update the record | FLAGUPD | CHAR | 1 | CHAR1 | ||||
| FLGTXTUPD | SDB: Indicator to update the record | FLAGUPD | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure DISOTXT using ABAP code?
As DISOTXT 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 DISOTXT as there is no data to select.How to access SAP table DISOTXT
Within an ECC or HANA version of SAP you can also view further information about DISOTXT 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