E2RDOCU SAP (Main seg. rel. order documentation for distributed contracts) Structure details
Description: Main seg. rel. order documentation for distributed contracts
Structure field list including key, data, relationships and ABAP select examples
E2RDOCU 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 "Main seg. rel. order documentation for distributed contracts" 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_E2RDOCU TYPE E2RDOCU.
The E2RDOCU table consists of various fields, each holding specific information or linking keys about Main seg. rel. order documentation for distributed contracts data available in SAP. These include KTPNR (R/2 table), EBELN (Purchasing Document Number), EBELP (R/2 table), BEDAT (Character field, 8 characters long).. 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 E2RDOCU 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 |
| KONNR | Number of Principal Purchase Agreement | KONNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | KTR | |
| KTPNR | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| EBELP | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| BEDAT | Character field, 8 characters long | CHAR8 | CHAR | 8 | CHAR8 | ||||
| MENGE | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| MEINS | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| NETWR | Item value (net) | EDI5004_D | CHAR | 18 | EDIF5004 | ||||
| WAERS | R/2 table | CHAR5 | CHAR | 5 | CHAR5 | ||||
| WKURS | Character Field of Length 12 | CHAR12 | CHAR | 12 | CHAR12 | ||||
| LOEKZ | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| LOGSY | Logical System | LOGSYSTEM | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| PLOEK | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| WEPOS | Goods Receipt Indicator | WEPOS | CHAR | 1 | XFELD | ||||
| REPOS | Invoice Receipt Indicator | REPOS | CHAR | 1 | XFELD | ||||
| WEMNG | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| REMNG | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
| BUKRS | Character field of length 6 | CHAR6 | CHAR | 6 | CHAR6 | ||||
| WERKS | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 |
| Key field | Non-key field |
How do I retrieve data from SAP structure E2RDOCU using ABAP code?
As E2RDOCU 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 E2RDOCU as there is no data to select.How to access SAP table E2RDOCU
Within an ECC or HANA version of SAP you can also view further information about E2RDOCU 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