EAMI_LOG_DB_DATA SAP (AMI Log and Message Data) Structure details
Description: AMI Log and Message Data
Related tables to EAMI_LOG_DB_DATA
Access table EAMI_LOG_DB_DATA
Structure field list including key, data, relationships and ABAP select examples
EAMI_LOG_DB_DATA 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 "AMI Log and Message Data" 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_EAMI_LOG_DB_DATA TYPE EAMI_LOG_DB_DATA.
The EAMI_LOG_DB_DATA table consists of various fields, each holding specific information or linking keys about AMI Log and Message Data data available in SAP. These include MANDT (Client), LOG_ID (Internal Number of AMI Log Entry), OBJECTTYPE (Object Type of Log Entry), OBJECTKEY (Object 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: Can Be Enhanced (Deep)
SAP EAMI_LOG_DB_DATA 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 |
| EAMI_LOG_DATA | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| LOG_ID | Internal Number of AMI Log Entry | E_AMI_LOG_ID | CHAR | 22 | SYSUUID_22 | ||||
| OBJECTTYPE | Object Type of Log Entry | E_AMI_OBJECTTYPE | CHAR | 2 | E_AMI_OBJECTTYPE | ||||
| OBJECTKEY | Object Key | E_AMI_OBJECTKEY | CHAR | 22 | TEXT22 | ||||
| OBJECTTYPE2 | Secondary Object Type of Log Entry | E_AMI_OBJECTTYPE_SEC | CHAR | 2 | E_AMI_OBJECTTYPE | ||||
| OBJECTKEY2 | Secondary Object Key | E_AMI_OBJECTKEY_SEC | CHAR | 22 | TEXT22 | ||||
| TRANS_DIRECTION | Direction of Data Transfer (Process Initiator) | E_AMI_TRANSDIRECTION | CHAR | 1 | EAMI_TRANSDIRECTION | ||||
| ACTION | Communication Action | E_AMI_ACTION | NUMC | 2 | E_AMI_ACTION | ||||
| PROCESS_STATUS | Process Status | E_AMI_PROCESS_STATUS | NUMC | 2 | EAMI_PROCESS_STATUS | ||||
| AMS | Advanced Metering System | E_AMI_AMS | CHAR | 4 | E_AMI_AMS | ||||
| TIMESTAMP_OUT | Outbound: UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun | E_AMI_TIMESTAMP_OUT | DEC | 21(7) | TZNTSTMPL | ||||
| MSGID_OUT | Message ID Outbound | E_AMI_MSGID_OUT | RAW | 16 | SYSUUID | ||||
| UUID_OUT | UUID Outbound | E_AMI_UUID_OUT | CHAR | 32 | SYSUUID_C | ||||
| SERVICE_ID_OUT | ID of Called eSOA Service (AMI) | E_AMI_SERVICE_ID_OUT | NUMC | 4 | E_AMI_SERVICE_ID | ||||
| REFUUID | Referenced UUID Inbound/Outbound | E_AMI_UUID_REF | CHAR | 32 | SYSUUID_C | ||||
| TIMESTAMP_IN | Inbound: UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | E_AMI_TIMESTAMP_IN | DEC | 21(7) | TZNTSTMPL | ||||
| MSGID_IN | Message ID Inbound | E_AMI_MSGID_IN | RAW | 16 | SYSUUID | ||||
| UUID_IN | UUID Inbound | E_AMI_UUID_IN | CHAR | 32 | SYSUUID_C | ||||
| SERVICE_ID_IN | INBOUND: ID of Called eSOA Service (AMI) | E_AMI_SERVICE_ID_IN | NUMC | 4 | E_AMI_SERVICE_ID | ||||
| CR_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| CR_TIME | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
| CR_NAME | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CH_DATE | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| CH_TIME | Time last change was made | AEZET | TIMS | 6 | UZEIT | ||||
| CH_NAME | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| TEAMI_LOG_MSG | 0 | ||||||||
| ARCHIVE | Indicators | KENNZX | CHAR | 1 | KENNZX |
| Key field | Non-key field |
How do I retrieve data from SAP structure EAMI_LOG_DB_DATA using ABAP code?
As EAMI_LOG_DB_DATA 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 EAMI_LOG_DB_DATA as there is no data to select.How to access SAP table EAMI_LOG_DB_DATA
Within an ECC or HANA version of SAP you can also view further information about EAMI_LOG_DB_DATA 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