ARRANGERR2 SAP (Error Messages Re Reb. Arrangement and Cond. Records (Item)) Structure details
Description: Error Messages Re Reb. Arrangement and Cond. Records (Item)
Structure field list including key, data, relationships and ABAP select examples
ARRANGERR2 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 "Error Messages Re Reb. Arrangement and Cond. Records (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_ARRANGERR2 TYPE ARRANGERR2.
The ARRANGERR2 table consists of various fields, each holding specific information or linking keys about Error Messages Re Reb. Arrangement and Cond. Records (Item) data available in SAP. These include KNUMH (Condition record number), KOPOS (Sequential number of the condition), LFERR (Sequence Number for Message (for Stable Sorting)), DATAB (Validity start date of the condition 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: Not classified
SAP ARRANGERR2 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 |
| KNUMA | Agreement (various conditions grouped together) | KNUMA | CHAR | 10 | Assigned to domain | ALPHA | KNUMA | VMBO | |
| KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
| KOPOS | Sequential number of the condition | KOPOS | NUMC | 2 | NUM02 | ||||
| LFERR | Sequence Number for Message (for Stable Sorting) | LFERR_WBON | INT4 | 10 | SYST_LONG | ||||
| DATAB | Validity start date of the condition record | KODATAB | DATS | 8 | DATUM | ||||
| DATBI | Validity end date of the condition record | KODATBI | DATS | 8 | DATUM | ||||
| MSGID | Message identification | MSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGTY | Message Type | MSGTY | CHAR | 1 | MSGAR | ||||
| MSGNO | System Message Number | MSGNO | CHAR | 3 | Assigned to domain | MSGNR | |||
| MSGV1 | Message variable 01 | MSGV1 | CHAR | 50 | CHAR50 | ||||
| MSGV2 | Message variable 02 | MSGV2 | CHAR | 50 | CHAR50 | ||||
| MSGV3 | Message variable 03 | MSGV3 | CHAR | 50 | CHAR50 | ||||
| MSGV4 | Message variable 04 | MSGV4 | CHAR | 50 | CHAR50 | ||||
| NATXT | Message text with inserted parameters | NATXTP | CHAR | 100 | CHAR100 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ARRANGERR2 using ABAP code?
As ARRANGERR2 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 ARRANGERR2 as there is no data to select.How to access SAP table ARRANGERR2
Within an ECC or HANA version of SAP you can also view further information about ARRANGERR2 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