QAMAS_TASK_MAP SAP (Quality Activity - Structure for Mapping to QIM) Structure details
Description: Quality Activity - Structure for Mapping to QIM
Related tables to QAMAS_TASK_MAP
Access table QAMAS_TASK_MAP
Structure field list including key, data, relationships and ABAP select examples
QAMAS_TASK_MAP 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 "Quality Activity - Structure for Mapping to QIM" 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_QAMAS_TASK_MAP TYPE QAMAS_TASK_MAP.
The QAMAS_TASK_MAP table consists of various fields, each holding specific information or linking keys about Quality Activity - Structure for Mapping to QIM data available in SAP. These include MANUM (Sequential Number of Activity), MATXT (Short Text for Activity), ERDAT (Date on Which Record Was Created), AEDAT (Last Changed On).. 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 QAMAS_TASK_MAP 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 |
| QMNUM | Message Number | 0 | |||||||
| MANUM | Sequential Number of Activity | 0 | |||||||
| MATXT | Short Text for Activity | 0 | |||||||
| ERDAT | Date on Which Record Was Created | 0 | |||||||
| AEDAT | Last Changed On | 0 | |||||||
| INDTX | Long Text for Object Exists | 0 | |||||||
| CODE_COMBINED | Concatenated Code | 0 | |||||||
| MNKAT | Catalog Type - Activities | 0 | |||||||
| MNGRP | Code Group - Activities | 0 | |||||||
| MNCOD | Activity Code | 0 | |||||||
| MNCODTX | Short Text for Code | 0 | |||||||
| PRIOK | Priority | 0 | |||||||
| PRIO_TXT | Short Text for Priority | 0 | |||||||
| PSTER | Planned Start Date | 0 | |||||||
| PETER | Planned End Date | 0 | |||||||
| QMART | Notification Type | 0 | |||||||
| QMART_TXT | Notification Type Text | 0 | |||||||
| OBJNR | Object Number for Status Management | 0 | |||||||
| MATNR | Material no. | 0 | |||||||
| MAKTX | Material Description | 0 | |||||||
| MAWERK | Plant for Material | 0 | |||||||
| WERK_TXT | Plant Text | 0 | |||||||
| LIFNUM | Account Number of Supplier or Vendor | 0 | |||||||
| LIF_NAME | Name of Supplier or Vendor | 0 | |||||||
| KUNUM | Account Number of Customer or Debtor | 0 | |||||||
| KUN_NAME | Name of Customer or Debtor | 0 | |||||||
| PARNR | Person Responsible for Activity (Partner Number) | 0 | |||||||
| PARNR_NAME | Name of Person Responsible | 0 | |||||||
| FENUM | Item Number in Item Record | 0 | |||||||
| URNUM | Sequential Number for Cause | 0 | |||||||
| PARENT_QI_ID | ID of Parent Issue | 0 | |||||||
| STAT | Status | 0 | |||||||
| ADDITIONAL_STATUS | Additional Status | 0 | |||||||
| MORE_THAN_ONE_MAT_IND | More Than One Referenced Material Exists | 0 | |||||||
| MORE_THAN_ONE_CUST_IND | More Than One Referenced Customer Exists | 0 | |||||||
| MORE_THAN_ONE_VEND_IND | More Than One Referenced Vendor Exists | 0 | |||||||
| CATEGORY | Category in Quality Issue Management (QIM) | 0 | |||||||
| LOGSYS | Logical System | 0 | |||||||
| EQUNR | Equipment Number | 0 | |||||||
| TPLNR | Functional Location | 0 | |||||||
| PSP_NR | WBS Element (Work Breakdown Structure Element) | 0 | |||||||
| EQKTX | Description of Technical Object | 0 | |||||||
| PLTXT | Functional Location Text | 0 | |||||||
| PSP_TXT | WBS: Short Description (First Text Line) | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure QAMAS_TASK_MAP using ABAP code?
As QAMAS_TASK_MAP 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 QAMAS_TASK_MAP as there is no data to select.How to access SAP table QAMAS_TASK_MAP
Within an ECC or HANA version of SAP you can also view further information about QAMAS_TASK_MAP 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