DIQMUR SAP (PM notification causes) Structure details
Description: PM notification causes
Structure field list including key, data, relationships and ABAP select examples
DIQMUR 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 "PM notification causes" 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_DIQMUR TYPE DIQMUR.
The DIQMUR table consists of various fields, each holding specific information or linking keys about PM notification causes data available in SAP. These include MANDT (Client), QMNUM (Notification No), FENUM (Item Number in Item Record), URNUM (Sequential Number for Cause).. 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 DIQMUR 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 | |
FENUM | Item Number in Item Record | FELFD | NUMC | 4 | QMFE | FELFD | |||
URNUM | Sequential Number for Cause | URNUM | NUMC | 4 | NUM4 | ||||
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 | ||||
URTXT | Cause Text | URSTX | CHAR | 40 | TEXT40 | ||||
URKAT | Catalog Type - Causes | URKAT | CHAR | 1 | TQ15 | QKATART | |||
URGRP | Code Group - Causes | URGRP | CHAR | 8 | QPGR | QCODEGRP | |||
URCOD | Cause Code | URCOD | CHAR | 4 | Assigned to domain | QCODE | |||
URVER | Version Number | QVERSNR | CHAR | 6 | ALPHA | QVERSNR | |||
INDTX | Object Long Text Available | INDLTX | CHAR | 1 | CHAR1 | ||||
KZMLA | Primary language indicator for text segment | KZMLA | CHAR | 1 | CHAR1 | ||||
ERZEIT | Time, at Which Record Was Added | ERZEIT | TIMS | 6 | UHRZT | ||||
AEZEIT | Time of Change | AEZEIT | TIMS | 6 | UHRZT | ||||
VUKAT | Catalog Type - Party Responsible | QVUKAT | CHAR | 1 | TQ15 | QKATART | |||
VUGRP | Code Group - Party Responsible | QVUGRP | CHAR | 8 | QPGR | QCODEGRP | |||
VUCOD | Code for Party Responsible | QVUCOD | CHAR | 4 | Assigned to domain | QCODE | |||
PARVW | Function for Party Responsible | QMUR_PARVW | CHAR | 2 | TPAR | PARVW | PARVW | PAR | |
PARNR | Party Responsible for Cause (Partner Number) | QMUR_PARNR | CHAR | 12 | ALPHA | I_PARNR | |||
BAUTL | Cause Assembly | QMUR_BAUTL | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT1 | |
URMENGE | Quantity | QURMNG | QUAN | 13(3) | MENGE | ||||
URMGEIN | Unit of Measure for Item | QMGEIN | UNIT | 3 | T006 | CUNIT | MEINS | ||
KZLOESCH | Delete Data Record | KZLOESCH | CHAR | 1 | CHAR1 | ||||
QURNUM | Sort Number for Cause | QURNUM | NUMC | 4 | NUMC04 | ||||
AUTKZ | Data Record Created with Function 'Create with Copy Model' | QAUTKZ | CHAR | 1 | QKZ | ||||
.INCLU--AP | 0 | ||||||||
INVOLVPERC | Involvment in Percentage | QN8D_INVOLVPERC | NUMC | 3 | |||||
AEKNZ | Change indicator | AEKNZ | CHAR | 1 | FLAG | ||||
PRTKZ | Print Indicator | PRTKZ | CHAR | 1 | XFELD | ||||
TXTGR | Short Description of the Code Group | QKTEXTGR | CHAR | 40 | QKURZTEXT | ||||
TXTCD | Cause Code Short Text | TXTCDUR | CHAR | 40 | TEXT40 | ||||
TXTCDGR | Short Text for Cause Code | QTXTCDGRUR | CHAR | 80 | QTEXT80 |
Key field | Non-key field |
How do I retrieve data from SAP structure DIQMUR using ABAP code?
As DIQMUR 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 DIQMUR as there is no data to select.How to access SAP table DIQMUR
Within an ECC or HANA version of SAP you can also view further information about DIQMUR 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