ME59_OUTTAB SAP (Output Structure for ME59) Structure details
Description: Output Structure for ME59
Structure field list including key, data, relationships and ABAP select examples
ME59_OUTTAB 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 "Output Structure for ME59" 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_ME59_OUTTAB TYPE ME59_OUTTAB.
The ME59_OUTTAB table consists of various fields, each holding specific information or linking keys about Output Structure for ME59 data available in SAP. These include SEQUENCE (Natural Number), EBELN (Purchase Order Number), LIFNR (Vendor Account Number), RESWK (Supplying (Issuing) Plant in Stock Transport Order).. 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: Cannot Be Enhanced
SAP ME59_OUTTAB 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 |
| SUPERFIELD | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| SEQUENCE | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| EBELN | Purchase Order Number | BSTNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | |
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | Assigned to domain | WERKS | |||
| BSART | Order Type (Purchasing) | BSART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| SORT1 | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| KONNR | Number of Principal Purchase Agreement | KONNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | KTR | |
| KTPNR | Item Number of Principal Purchase Agreement | KTPNR | NUMC | 5 | Assigned to domain | EBELP | |||
| BANFN | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| BNFPO | Item Number of Purchase Requisition | BNFPO | NUMC | 5 | Assigned to domain | BNFPO | BAP | ||
| DETLOGICON | Detailed Log | ME59DETLOGICON | CHAR | 30 | |||||
| OBJTXT | Object Type | ME59OBJTXT | CHAR | 72 | |||||
| STATUSICON | Status icon | STATUSICON | CHAR | 60 | |||||
| MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
| T_MSG | Application Log: Formatted message text | BALTMSG | CHAR | 255 | BALTMSG | ||||
| MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
| MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| N_ITEMS | Number of Items | ME59ITEMS | INT4 | 10 | |||||
| N_REQS | Number of Purchase Requisitions | ME59REQS | INT4 | 10 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ME59_OUTTAB using ABAP code?
As ME59_OUTTAB 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 ME59_OUTTAB as there is no data to select.How to access SAP table ME59_OUTTAB
Within an ECC or HANA version of SAP you can also view further information about ME59_OUTTAB 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