MMREQ_HISTORY SAP (Flat Structure for Purchase Requisition Document Flow) Structure details
Description: Flat Structure for Purchase Requisition Document Flow
Related tables to MMREQ_HISTORY
Access table MMREQ_HISTORY
Structure field list including key, data, relationships and ABAP select examples
MMREQ_HISTORY 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 "Flat Structure for Purchase Requisition Document Flow" 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_MMREQ_HISTORY TYPE MMREQ_HISTORY.
The MMREQ_HISTORY table consists of various fields, each holding specific information or linking keys about Flat Structure for Purchase Requisition Document Flow data available in SAP. These include BSTYP_TEXT (Long text for document category), EBELN (Purchasing Document Number), ERNAM (Name of Person who Created the Object), LIFNR (Account Number of Vendor or Creditor).. 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 (character-type or numeric)
SAP MMREQ_HISTORY 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 |
| BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
| BSTYP_TEXT | Long text for document category | BSYTP_TEXT | CHAR | 30 | TEXT30 | ||||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| LOEKZ | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| KDATB | Start of Validity Period | KDATB | DATS | 8 | DATUM | ||||
| KDATE | End of Validity Period | KDATE | DATS | 8 | DATUM | ||||
| BWBDT | Closing Date for Applications | BWBDT | DATS | 8 | DATUM | ||||
| ANGDT | Quotation Validity Date | ANGDT | DATS | 8 | DATUM | ||||
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
| BEDNR | Requirement Tracking Number | BEDNR | CHAR | 10 | CHAR10 | ||||
| MATKL | Material Group | MATKL | CHAR | 9 | Assigned to domain | MATKL | MKL | S_WBWG | |
| ELIKZ | 'Delivery Completed' Indicator | ELIKZ | CHAR | 1 | XFELD | ||||
| EREKZ | Final Invoice Indicator | EREKZ | CHAR | 1 | XFELD | ||||
| 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 | |||
| VGABETEXT | Short Text for Fixed Values | VAL_TEXT | CHAR | 60 | DDTEXT | ||||
| BEWTP | PO history category | BEWTP | CHAR | 1 | Assigned to domain | BEWTP | |||
| BEWTK | Short Text for Purchase Order History Category | BEWTK | CHAR | 4 | TEXT4 | ||||
| BWART | Movement Type (Inventory Management) | BWART | CHAR | 3 | Assigned to domain | BWART | BWA | ||
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| MENGE | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| MEINS | Purchase Order Unit of Measure | BSTME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| VGABE | Transaction/event type, purchase order history | VGABE | CHAR | 1 | VGABE | ||||
| ETENR | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
| EINDT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| STATUSICON | Status icon | STATUSICON30 | CHAR | 30 | |||||
| .INCLU--AP | 0 | ||||||||
| LONGNUM | Smart Number | /SAPPSPRO/LONGNUM | CHAR | 40 | /SAPPSPRO/LONGNUM | /SAPPSPRO/LONG_BES | /SAPPSPRO/MEKK |
| Key field | Non-key field |
How do I retrieve data from SAP structure MMREQ_HISTORY using ABAP code?
As MMREQ_HISTORY 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 MMREQ_HISTORY as there is no data to select.How to access SAP table MMREQ_HISTORY
Within an ECC or HANA version of SAP you can also view further information about MMREQ_HISTORY 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