CLAIM_IS1 SAP (Reporting Structure for CLAIMIS1) Structure details
Description: Reporting Structure for CLAIMIS1
Structure field list including key, data, relationships and ABAP select examples
CLAIM_IS1 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 "Reporting Structure for CLAIMIS1" 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_CLAIM_IS1 TYPE CLAIM_IS1.
The CLAIM_IS1 table consists of various fields, each holding specific information or linking keys about Reporting Structure for CLAIMIS1 data available in SAP. These include QMART (Notification Type), QMARTX (Notification Type Texts), REFNUM (External Reference Number), QMTXT (Short Text).. 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 CLAIM_IS1 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 | Notification No | QMNUM | CHAR | 12 | Assigned to domain | ALPHA | QMNUM | IQM | |
QMART | Notification Type | QMART | CHAR | 2 | Assigned to domain | QMART | QMR | ||
QMARTX | Notification Type Texts | QMARTX | CHAR | 20 | TEXT20 | ||||
REFNUM | External Reference Number | QMEXTNR | CHAR | 20 | CHAR020 | ||||
QMTXT | Short Text | QMTXT | CHAR | 40 | TEXT40 | ||||
OPPONENT | Partner Type | PS_OPPONENT | CHAR | 2 | OPPONENT | ||||
OPPONENT_TXT | Short Text for Fixed Values | VAL_TEXT | CHAR | 60 | DDTEXT | ||||
PRIOK | Priority | PRIOK | CHAR | 1 | Assigned to domain | PRIOK | PRIOK | ||
PRIOKX | Priority Text | PRIOKX | CHAR | 20 | TEXT20 | ||||
CHANCE | Chance of Completing a Claim | PS_CHANCE | NUMC | 2 | PS_CHANCE | ||||
CHANCE_TXT | Short Text for Fixed Values | VAL_TEXT | CHAR | 60 | DDTEXT | ||||
URTXT | Cause Text | URSTX | CHAR | 40 | TEXT40 | ||||
URKAT | Catalog Type - Causes | URKAT | CHAR | 1 | Assigned to domain | QKATART | |||
URGRP | Code Group - Causes | URGRP | CHAR | 8 | Assigned to domain | QCODEGRP | |||
URCOD | Cause Code | URCOD | CHAR | 4 | Assigned to domain | QCODE | |||
URCOD_TXT | Short Text for Code (Up to 40 Characters in Length) | QTXT_CODE | CHAR | 40 | QKURZTEXT | ||||
INDTX | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
INDTX_1 | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
INDTX_2 | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
INDTX_3 | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
INDTX_4 | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
COSTS_ESTIMATE | Estimated Costs for a Claim | PS_COSTS | CURR | 13(2) | WERTV7 | ||||
COSTS_CLAIMED | Costs Claimed | COSTS_CLAIM | CURR | 13(2) | WERTV7 | ||||
COSTS_RESULT | Costs Accepted | COSTS_RESULT | CURR | 13(2) | WERTV7 | ||||
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 | ||||
MZEIT | Time of Notification | MZEIT | TIMS | 6 | UHRZT | ||||
QMDAT | Date of Notification | QMDAT | DATS | 8 | DATUM | ||||
QMNAM | Name of Person Reporting Notification | QMNAM | CHAR | 12 | USNAM | ||||
STTXT | System Status for Notification | QMSTTXT | CHAR | 40 | TEXT40 | ||||
ASTXT | Field displaying user status | CO_ASTTX | CHAR | 40 | CHAR40 | ||||
STRMN | Required start date | STRMN | DATS | 8 | DATUM | ||||
STRUR | Required Start Time | STRUR | TIMS | 6 | UZEIT | ||||
LTRMN | Required End Date | LTRMN | DATS | 8 | DATUM | ||||
LTRUR | Requested End Time | LTRUR | TIMS | 6 | UZEIT | ||||
BSTNK | Customer purchase order number | BSTKD | CHAR | 35 | BSTKD | ||||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
EBELP | Item Number of Purchasing Document | QEBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
LS_KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
LS_KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
LS_VBELN | Delivery | VBELN_VL | CHAR | 10 | Assigned to domain | ALPHA | VBELN | VL | |
LS_POSNR | Delivery Item | QPOSNR_VL | NUMC | 6 | Assigned to domain | POSNR | |||
QWRNUM | Reference Notification Number | QWRNUM | CHAR | 12 | Assigned to domain | ALPHA | QMNUM | IQM | |
PSP_NR | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
PSP_TXT | PS: Short description (1st text line) | PS_POST1 | CHAR | 40 | TEXT40 | ||||
OBJNR | Object Number for Status Management | QMOBJNR | CHAR | 22 | Assigned to domain | J_OBJNR |
Key field | Non-key field |
How do I retrieve data from SAP structure CLAIM_IS1 using ABAP code?
As CLAIM_IS1 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 CLAIM_IS1 as there is no data to select.How to access SAP table CLAIM_IS1
Within an ECC or HANA version of SAP you can also view further information about CLAIM_IS1 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