HDB_M_MERGED_TRACES SAP (Fields of M_MERGED_TRACES) Structure details
Description: Fields of M_MERGED_TRACES
Related tables to HDB_M_MERGED_TRACES
Access table HDB_M_MERGED_TRACES
Structure field list including key, data, relationships and ABAP select examples
HDB_M_MERGED_TRACES 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 "Fields of M_MERGED_TRACES" 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_HDB_M_MERGED_TRACES TYPE HDB_M_MERGED_TRACES.
The HDB_M_MERGED_TRACES table consists of various fields, each holding specific information or linking keys about Fields of M_MERGED_TRACES data available in SAP. These include TRACE_TEXT (), HOST (Name of database host), PORT (Name of database port), USER_NAME ().. 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 HDB_M_MERGED_TRACES 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 |
TIMESTAMP | Time stamp (stored in format YYYY-MM-DD HH:MM:SS) | HDB_TSTMP | CHAR | 19 | HDBDA | HDB_TSTMP | |||
TRACE_TEXT | 0 | ||||||||
HOST | Name of database host | HDB_HOST | CHAR | 64 | HDB_HOST | HDB_HOST | |||
PORT | Name of database port | HDB_PORT | INT4 | 10 | HDB_PORT | ||||
USER_NAME | 0 | ||||||||
APPLICATION_USER_NAME | 0 | ||||||||
SERVICE_NAME | Service Name | HDB_SERVICE_TYPES | CHAR | 255 | HDB_SERVICES | HDB_SERVICES | |||
CONNECTION_ID | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
TRANSACTION_ID | HDB: Big Integer | HDB_BIGINT | DEC | 22 | |||||
THREAD_ID | HDB: Big Integer | HDB_BIGINT | DEC | 22 | |||||
TRACE_LEVEL | Trace Level | HDB_TRACE_LEVEL | CHAR | 8 | HDB_TRACE_LEVEL | ||||
COMPONENT | Component | HDB_COMPONENT | CHAR | 32 | TEXT32 | HDB_COMPONENT | |||
SOURCE_FILE_NAME | 0 | ||||||||
SOURCE_FILE_LINE | HDB: Big Integer | HDB_BIGINT | DEC | 22 | |||||
TRACE_FILE_NAME | 0 | ||||||||
TRACE_FILE_LINE | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
PASSPORT_ROOT_CONTEXT_ID | 0 | ||||||||
PASSPORT_TRANSACTION_ID | 0 | ||||||||
PASSPORT_CONNECTION_ID | 0 | ||||||||
PASSPORT_CONNECTION_COUNTER | HDB: Big Integer | HDB_BIGINT | DEC | 22 | |||||
PASSPORT_COMPONENT_NAME | 0 | ||||||||
PASSPORT_ACTION | 0 | ||||||||
LENGTH_LOB | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure HDB_M_MERGED_TRACES using ABAP code?
As HDB_M_MERGED_TRACES 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 HDB_M_MERGED_TRACES as there is no data to select.How to access SAP table HDB_M_MERGED_TRACES
Within an ECC or HANA version of SAP you can also view further information about HDB_M_MERGED_TRACES 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