MDAT1 SAP (Fields for Screens and Parameters: Data Transfer) Structure details
Description: Fields for Screens and Parameters: Data Transfer
Structure field list including key, data, relationships and ABAP select examples
MDAT1 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 for Screens and Parameters: Data Transfer" 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_MDAT1 TYPE MDAT1.
The MDAT1 table consists of various fields, each holding specific information or linking keys about Fields for Screens and Parameters: Data Transfer data available in SAP. These include MESSLEVEL (Display level for data transfer messages), SPERA (Lock mode), N_EING_F (Response if Fields Are Not Ready for Input), KZ_VERW (Indicator: Set up administrative data).. 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 (character-type or numeric)
SAP MDAT1 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 |
| MAX_COMM | No. of transactions per commit unit for data transfer | MD_MAXCOMM | NUMC | 6 | NUMC6 | ||||
| MESSLEVEL | Display level for data transfer messages | MD_MESSLEV | CHAR | 1 | MD_MESSLEV | ||||
| SPERA | Lock mode | MD_SPERR | CHAR | 1 | MD_SPERR | ||||
| N_EING_F | Response if Fields Are Not Ready for Input | N_EING_F | CHAR | 1 | N_EING_F | ||||
| KZ_VERW | Indicator: Set up administrative data | MD_VERW | CHAR | 1 | XFELD | ||||
| KZ_AEND | Create Change Documents in Data Transfer | MD_AENDER | CHAR | 1 | XFELD | ||||
| KZ_DISPO | Indicator: Update planning file entries during data transfer | MD_DISPO | CHAR | 1 | XFELD | ||||
| KZ_MUSS | Check required fields not belonging to core maint. status | MD_MUSS_S | CHAR | 1 | XFELD | ||||
| KZ_TEST | Indicator: Make checks, but do not update data | MD_TEST | CHAR | 1 | XFELD | ||||
| KZ_RONLY | Ind.: Read file only | MD_RONLY | CHAR | 1 | XFELD | ||||
| KZ_NUMV | Number assignment for creating a test file | MD_NUMV | CHAR | 1 | MD_NUMV | ||||
| KZ_PSTA | Fill status fields in BMM00 | MD_PSTA | CHAR | 1 | XFELD | ||||
| ERFMELD | Issue success messages | MD_ERFMELD | CHAR | 1 | XFELD | ||||
| MAX_ERR | Maximum number of logical errors with direct input | MD_MAXERR | DEC | 5 | DEC5 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MDAT1 using ABAP code?
As MDAT1 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 MDAT1 as there is no data to select.How to access SAP table MDAT1
Within an ECC or HANA version of SAP you can also view further information about MDAT1 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