GTCOMMON_MESSAGE SAP (This attribute group defines attributes that are commona c) Structure details
Description: This attribute group defines attributes that are commona c
Related tables to GTCOMMON_MESSAGE
Access table GTCOMMON_MESSAGE
Structure field list including key, data, relationships and ABAP select examples
GTCOMMON_MESSAGE 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 "This attribute group defines attributes that are commona c" 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_GTCOMMON_MESSAGE TYPE GTCOMMON_MESSAGE.
The GTCOMMON_MESSAGE table consists of various fields, each holding specific information or linking keys about This attribute group defines attributes that are commona c data available in SAP. These include TIME_STAMP (Indicates the creation date and time of the message in UTC u), TARGET (Used to indicate whether the request is for the Test or Prod), VERSION (For all OTA versioned messages, the version of the message i), SEQUENCE_NMBR (Used to identify the sequence number of the transaction as a).. 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: Can Be Enhanced (Deep)
SAP GTCOMMON_MESSAGE 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 |
| ECHO_TOKEN | A sequence number for additional message identification, ass | 0 | |||||||
| TIME_STAMP | Indicates the creation date and time of the message in UTC u | 0 | |||||||
| TARGET | Used to indicate whether the request is for the Test or Prod | 0 | |||||||
| VERSION | For all OTA versioned messages, the version of the message i | 0 | |||||||
| SEQUENCE_NMBR | Used to identify the sequence number of the transaction as a | 0 | |||||||
| PRIMARY_LANG_ID | Identifes the primary language preference for the form of tr | 0 | |||||||
| ALT_LANG_ID | Identifes the primary language preference for the form of tr | 0 | |||||||
| CORRELATION_ID | Used for Character Strings, length 1 to 64. | CLASCO_STRING_LENGTH1TO64 | CHAR | 64 |
| Key field | Non-key field |
How do I retrieve data from SAP structure GTCOMMON_MESSAGE using ABAP code?
As GTCOMMON_MESSAGE 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 GTCOMMON_MESSAGE as there is no data to select.How to access SAP table GTCOMMON_MESSAGE
Within an ECC or HANA version of SAP you can also view further information about GTCOMMON_MESSAGE 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