MEREP_OUTTAB_MESSAGES SAP (Output Structure: Message Processing in Purchasing) Structure details
Description: Output Structure: Message Processing in Purchasing
Related tables to MEREP_OUTTAB_MESSAGES
Access table MEREP_OUTTAB_MESSAGES
Structure field list including key, data, relationships and ABAP select examples
MEREP_OUTTAB_MESSAGES 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: Message Processing in Purchasing" 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_MEREP_OUTTAB_MESSAGES TYPE MEREP_OUTTAB_MESSAGES.
The MEREP_OUTTAB_MESSAGES table consists of various fields, each holding specific information or linking keys about Output Structure: Message Processing in Purchasing data available in SAP. These include MANDT (Client), EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), SUPERFIELD (Vendor/Supplying Plant).. 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: Can Be Enhanced (Deep)
SAP MEREP_OUTTAB_MESSAGES 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 |
| SELKZ | Selection flag | SELKZ | CHAR | 1 | SELKZ | ||||
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| SUPERFIELD | Vendor/Supplying Plant | MEREP_SUPER | CHAR | 51 | TEXT51 | ||||
| EMATN | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
| ETENR | Delivery Schedule Line Counter | EETEN | NUMC | 4 | Assigned to domain | EETEN | |||
| EINDT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| MENGE | Quantity Still to be Expedited | MEREP_MAHNMG | QUAN | 13(3) | MENGE | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| BSTYP | Purchasing Document Category | EBSTYP | CHAR | 1 | EBSTYP | ||||
| BSART | Purchasing Document Type | ESART | CHAR | 4 | T161 | BSART | BSA | ||
| BSAKZ | Control indicator for purchasing document type | BSAKZ | CHAR | 1 | BSAKZ | ||||
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
| RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | Assigned to domain | WERKS | |||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
| EKGRP | Purchasing Group | BKGRP | CHAR | 3 | T024 | EKGRP | EKG | ||
| WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| WKURS | Exchange Rate | WKURS | DEC | 9(5) | EXCRT | KURSP | |||
| AEDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| BEDAT | Purchasing Document Date | EBDAT | DATS | 8 | DATUM | ||||
| ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| MDATUM | Reminder/Expediting Date | MDATUM | DATS | 8 | DATUM | ||||
| MAHNZ | Counter for reminders/urging letters (expediters) | MZAEHLER | DEC | 3 | PACK2 | ||||
| STATUS_TEXT | Processing Status | MEREP_STATUS_TEXT | CHAR | 40 | |||||
| ICON_STATUS | Processing Status | MEREP_ICON_STATUS | CHAR | 40 | |||||
| CELL_LAYOUT | 0 | ||||||||
| MAHN | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| AZPOS | No. of Positions | MEREP_AZPOS | INT4 | 10 | |||||
| SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MEREP_OUTTAB_MESSAGES using ABAP code?
As MEREP_OUTTAB_MESSAGES 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 MEREP_OUTTAB_MESSAGES as there is no data to select.How to access SAP table MEREP_OUTTAB_MESSAGES
Within an ECC or HANA version of SAP you can also view further information about MEREP_OUTTAB_MESSAGES 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