ARRANGMAIL SAP (Document items for condition records during update) Structure details
Description: Document items for condition records during update
Structure field list including key, data, relationships and ABAP select examples
ARRANGMAIL 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 "Document items for condition records during update" 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_ARRANGMAIL TYPE ARRANGMAIL.
The ARRANGMAIL table consists of various fields, each holding specific information or linking keys about Document items for condition records during update data available in SAP. These include EBELN (Document number of update-relevant document), EBELP (Item number of document relevant to cum. updating process), WKOPAR_LI (Assignment of business volumes, messages to condition level), BLTYPD (Doc. cat.: updating of business volumes).. 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 ARRANGMAIL 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 |
BLTYPN | Document category price determination (subseq. settlement) | BLTYPN | CHAR | 2 | BLTYPN | ||||
EBELN | Document number of update-relevant document | BELNR_NTR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | ||
EBELP | Item number of document relevant to cum. updating process | POSNR_NTR | NUMC | 6 | NUMC6 | ||||
WKOPAR_LI | Assignment of business volumes, messages to condition level | WKOPAR_LI | CHAR | 1 | WKOPAR_LI | ||||
BLTYPD | Doc. cat.: updating of business volumes | BLTYPD | CHAR | 2 | BLTYPD | ||||
BELNR | Number of a document (updating of business volumes) | FBLNR | CHAR | 10 | ALPHA | BELNR | |||
GJAHR | Document year: updating of business volumes | FJAHR | NUMC | 4 | GJAHR | GJAHR | |||
BUZEI | Document item (updating of cum. vendor business volumes) | FBLPO | NUMC | 6 | NUMC6 | ||||
ZEKKN | Sequential Number of Account Assignment | DZEKKN | NUMC | 2 | NUM02 | ||||
VGABE | Transaction/event type, purchase order history | VGABE | CHAR | 1 | VGABE | ||||
ETENR | Delivery Schedule Line Counter | FETEN | NUMC | 4 | Assigned to domain | EETEN | |||
EINDT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
BLTYPF | Doc. type: updating of vendor business volumes | BLTYPF | CHAR | 2 | BLTYPF | ||||
KNUMA | Agreement (various conditions grouped together) | KNUMA | CHAR | 10 | Assigned to domain | ALPHA | KNUMA | VMBO | |
BOART | Agreement type | BOART | CHAR | 4 | Assigned to domain | BOART | VBA | ||
KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
KOPOS | Sequential number of the condition | KOPOS | NUMC | 2 | NUM02 | ||||
STATUS | Status of the created update data | FOSOK | CHAR | 1 | FOSOK | ||||
TUROV_ST | Indicator: Updating of business volumes | TUROV_ST | CHAR | 1 | XFELD | ||||
KRUEK_ST | Indicator: Updating of provision for returned incomed | KRUEK_ST | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure ARRANGMAIL using ABAP code?
As ARRANGMAIL 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 ARRANGMAIL as there is no data to select.How to access SAP table ARRANGMAIL
Within an ECC or HANA version of SAP you can also view further information about ARRANGMAIL 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