MONITORENV SAP (Application Monitor: General Analysis Area) Structure details
Description: Application Monitor: General Analysis Area
Structure field list including key, data, relationships and ABAP select examples
MONITORENV 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 "Application Monitor: General Analysis Area" 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_MONITORENV TYPE MONITORENV.
The MONITORENV table consists of various fields, each holding specific information or linking keys about Application Monitor: General Analysis Area data available in SAP. These include LANGU (Language Key), DATUM (Date), DATUM_VON (Date as of which data is to be selected), DATUM_BIS (Date up to which data is to be selected).. 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 MONITORENV 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
LANGU | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
DATUM | Date | DATUM | DATS | 8 | DATUM | ||||
DATUM_VON | Date as of which data is to be selected | DATUM_VON | DATS | 8 | DATUM | ||||
DATUM_BIS | Date up to which data is to be selected | DATUM_BIS | DATS | 8 | DATUM | ||||
PERIODTYPE | SAP Workload: Period type | SAPWLACCPT | CHAR | 1 | SAPWLACCPT | ||||
KVEWE | Usage of the condition table | KVEWE | CHAR | 1 | Assigned to domain | KVEWE | KVW | ||
KAPPL | Application | KAPPL | CHAR | 2 | Assigned to domain | KAPPL | KAP | ||
PROT_EXIST | SD Monitor: The processing log exists | PROT_EXIST | CHAR | 1 | YESNO | ||||
MANDT_DIFF | SD Monitor: Different clients for analysis and protocol | MANDT_DIFF | CHAR | 1 | YESNO | ||||
VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
PAPPL | SD Monitor: SD Log Initiator | SDPROTCAL_ | CHAR | 4 | Assigned to domain | SDPROTCAL | |||
PAPPLMAINT | SD Monitor: The log application is supported by the analysis | PAPPLMAINT | CHAR | 1 | YESNO | ||||
KALSM | Procedure (Pricing, Output Control, Acct. Det., Costing,...) | KALSM_D | CHAR | 6 | Assigned to domain | KALSM | |||
RESRVD_C01 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C02 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C03 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C04 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C05 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C06 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C07 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C08 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C09 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_C10 | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
RESRVD_I01 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I02 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I03 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I04 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I05 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I06 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I07 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I08 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I09 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
RESRVD_I10 | Natural Number | INT4 | INT4 | 10 | INT4 |
Key field | Non-key field |
How do I retrieve data from SAP structure MONITORENV using ABAP code?
As MONITORENV 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 MONITORENV as there is no data to select.How to access SAP table MONITORENV
Within an ECC or HANA version of SAP you can also view further information about MONITORENV 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