SAP MMREQ_HISTORY Table in S/4 HANA - Flat Structure for Purchase Requisition Document Flow
MMREQ_HISTORY is a standard SAP Table which is used to store Flat Structure for Purchase Requisition Document Flow data and is available within SAP S/4 HANA systems and previous ECC R/3 systems. Below is the technical details and the field list relevant for an SAP S/4 HANA system, see here for details and fields available within the SAP R/3 version of the MMREQ_HISTORY table(ECC)
Delivery Class:
Display/Maintenance via SM30: Display/Maintenance Allowed but with Restrictions
Enhancement category: Can be enhanced (character-type or numeric)
Dictionary Type: Structure
Database Table: MMREQ_HISTORY
MMREQ_HISTORY table structure field list
Below is the full MMREQ_HISTORY field list that makes up the SAP database table structure, including key fields, description, data type and other technical details of each field
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP | SHLP Field |
BSTYP | Purchasing Document Category | BSTYP | CHAR | 1(0) | BSTYP | |||||
BSTYP_TEXT | Long text for document category | BSYTP_TEXT | CHAR | 30(0) | TEXT30 | |||||
EBELN | Purchasing Document Number | EBELN | CHAR | 10(0) | Assigned to domain | ALPHA | EBELN | BES | MEKK_C | EBELN |
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12(0) | USNAM | |||||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10(0) | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C | LIFNR |
LOEKZ | Deletion indicator in purchasing document | ELOEK | CHAR | 1(0) | ELOEK | |||||
KDATB | Start of Validity Period | KDATB | DATS | 8(0) | DATUM | |||||
KDATE | End of Validity Period | KDATE | DATS | 8(0) | DATUM | |||||
BWBDT | Closing Date for Applications | BWBDT | DATS | 8(0) | DATUM | |||||
ANGDT | Quotation Validity Date | ANGDT | DATS | 8(0) | DATUM | |||||
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5(0) | Assigned to domain | EBELP | BSP | |||
MATNR | Material Number | MATNR | CHAR | 40(0) | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 | MATNR |
BUKRS | Company Code | BUKRS | CHAR | 4(0) | Assigned to domain | BUKRS | BUK | C_T001 | BUKRS | |
WERKS | Plant | WERKS_D | CHAR | 4(0) | Assigned to domain | WERKS | WRK | H_T001W_C | WERKS | |
LGORT | Storage location | LGORT_D | CHAR | 4(0) | Assigned to domain | LGORT | LAG | |||
BEDNR | Requirement Tracking Number | BEDNR | CHAR | 10(0) | CHAR10 | |||||
MATKL | Material Group | MATKL | CHAR | 9(0) | Assigned to domain | MATKL | MKL | S_WBWG | MATKL | |
ELIKZ | 'Delivery Completed' Indicator | ELIKZ | CHAR | 1(0) | XFELD | |||||
EREKZ | Final Invoice Indicator | EREKZ | CHAR | 1(0) | XFELD | |||||
KONNR | Number of principal purchase agreement | KONNR | CHAR | 10(0) | Assigned to domain | ALPHA | EBELN | KTR | ||
KTPNR | Item number of principal purchase agreement | KTPNR | NUMC | 5(0) | Assigned to domain | EBELP | ||||
VGABETEXT | Short Text for Fixed Values | VAL_TEXT | CHAR | 60(0) | DDTEXT | |||||
BEWTP | Purchase Order History Category | BEWTP | CHAR | 1(0) | Assigned to domain | BEWTP | ||||
BEWTK | Short Text for Purchase Order History Category | BEWTK | CHAR | 4(0) | TEXT4 | |||||
BWART | Movement type (inventory management) | BWART | CHAR | 3(0) | Assigned to domain | BWART | BWA | |||
BUDAT | Posting Date in the Document | BUDAT | DATS | 8(0) | DATUM | |||||
MENGE | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | |||||
MEINS | Purchase Order Unit of Measure | BSTME | UNIT | 3(0) | Assigned to domain | CUNIT | MEINS | |||
VGABE | Transaction/event type, purchase order history | VGABE | CHAR | 1(0) | VGABE | |||||
ETENR | Schedule Line Number | ETENR | NUMC | 4(0) | Assigned to domain | ETENR | ||||
EINDT | Item delivery date | EINDT | DATS | 8(0) | DATUM | |||||
STATUSICON | Status icon | STATUSICON30 | CHAR | 30(0) | ||||||
.INCLU--AP | 0(0) | |||||||||
LONGNUM | Smart Number | /SAPPSPRO/LONGNUM | CHAR | 40(0) | /SAPPSPRO/LONGNUM | /SAPPSPRO/LONG_BES | /SAPPSPRO/MEKK | LONGNUM |
Search for further information about these or an SAP related objects