DIQMMA SAP (Activities for notification item) Structure details
Description: Activities for notification item
Structure field list including key, data, relationships and ABAP select examples
DIQMMA 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 "Activities for notification item" 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_DIQMMA TYPE DIQMMA.
The DIQMMA table consists of various fields, each holding specific information or linking keys about Activities for notification item data available in SAP. These include MANDT (Client), QMNUM (Notification No), MANUM (Consecutive Number of Activity), FENUM (Item Number in Item Record).. 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 DIQMMA 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 | T000 | MANDT | |||
QMNUM | Notification No | QMNUM | CHAR | 12 | QMEL | ALPHA | QMNUM | IQM | |
MANUM | Consecutive Number of Activity | AKNUM | NUMC | 4 | NUM4 | ||||
FENUM | Item Number in Item Record | FELFD | NUMC | 4 | QMFE | FELFD | |||
URNUM | Sequential Number for Cause | URNUM | NUMC | 4 | NUM4 | ||||
MNKAT | Catalog Type - Activities | MFKAT | CHAR | 1 | TQ15 | QKATART | |||
MNGRP | Code Group - Activities | MFGRP | CHAR | 8 | QPGR | QCODEGRP | |||
MNCOD | Activity Code | MFCOD | CHAR | 4 | Assigned to domain | QCODE | |||
MNVER | Version Number | QVERSNR | CHAR | 6 | ALPHA | QVERSNR | |||
MATXT | Activity Text | MFTEXT | CHAR | 40 | TEXT40 | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
MAKLS | Task Class | MAKLS | CHAR | 18 | KLASSE | ||||
KLAKZ | Indicator: Classification exists | KLAKZ | CHAR | 1 | CHAR1 | ||||
PSTER | Start Date | PSTERMA | DATS | 8 | DATUM | ||||
PETER | End Date | PETERMA | DATS | 8 | DATUM | ||||
INDTX | Object Long Text Available | INDLTX | CHAR | 1 | CHAR1 | ||||
KZMLA | Primary language indicator for text segment | KZMLA | CHAR | 1 | CHAR1 | ||||
MNGFA | Quantity Factor for Activities | MNGFA | NUMC | 3 | NUMC3 | ||||
PSTUR | Start Time of Activity | PSTURMA | TIMS | 6 | UZEIT | ||||
PETUR | End Time of Activity | PETURMA | TIMS | 6 | UZEIT | ||||
ERZEIT | Time, at Which Record Was Added | ERZEIT | TIMS | 6 | UHRZT | ||||
AEZEIT | Time of Change | AEZEIT | TIMS | 6 | UHRZT | ||||
KZLOESCH | Delete Data Record | KZLOESCH | CHAR | 1 | CHAR1 | ||||
QMANUM | Sort Number for Activity | QMANUM | NUMC | 4 | NUMC04 | ||||
AUTKZ | Data Record Created with Function 'Create with Copy Model' | QAUTKZ | CHAR | 1 | QKZ | ||||
KZACTIONBOX | Created Using Action Box | QNKZACTIONBOX | CHAR | 1 | QKZ | ||||
FUNKTION | Keys for Function in Action Box | QNFUNKTION | CHAR | 4 | CHAR4 | ||||
TXTGR | Short Description of the Code Group | QKTEXTGR | CHAR | 40 | QKURZTEXT | ||||
TXTCD | Activity Code Short Text | TXTCDMA | CHAR | 40 | TEXT40 |
Key field | Non-key field |
How do I retrieve data from SAP structure DIQMMA using ABAP code?
As DIQMMA 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 DIQMMA as there is no data to select.How to access SAP table DIQMMA
Within an ECC or HANA version of SAP you can also view further information about DIQMMA 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