RPREQ SAP (Purchase Requisitions in Rescheduling) Structure details
Description: Purchase Requisitions in Rescheduling
Structure field list including key, data, relationships and ABAP select examples
RPREQ 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 "Purchase Requisitions in Rescheduling" 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_RPREQ TYPE RPREQ.
The RPREQ table consists of various fields, each holding specific information or linking keys about Purchase Requisitions in Rescheduling data available in SAP. These include MANDT (Client), MATNR (Material Number), RESWK (Supplying (Issuing) Plant in Stock Transport Order), BANFN (Purchase Requisition Number).. 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 RPREQ 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| MATNR | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
| RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | T001W | WERKS | |||
| BANFN | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| BNFPO | Item Number of Purchase Requisition | BNFPO | NUMC | 5 | EBAN | BNFPO | BAP | ||
| BSAKZ | Control indicator for purchasing document type | BSAKZ | CHAR | 1 | BSAKZ | ||||
| LOEKZ | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| ESTKZ | Creation Indicator (Purchase Requisition/Schedule Lines) | ESTKZ | CHAR | 1 | ESTKZ | ||||
| WERKS | Plant | EWERK | CHAR | 4 | T001W | WERKS | WRK | ||
| LGORT | Storage Location | LGORT_D | CHAR | 4 | T001L | LGORT | LAG | ||
| MENGE | Purchase Requisition Quantity | BAMNG | QUAN | 13(3) | MENG13 | ||||
| MEINS | Purchase Requisition Unit of Measure | BAMEI | UNIT | 3 | T006 | CUNIT | MEINS | ||
| LFDAT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| FRGDT | Purchase Requisition Release Date | FRGDT | DATS | 8 | DATUM | ||||
| KNTTP | Account Assignment Category | KNTTP | CHAR | 1 | T163K | KNTTP | KNT | ||
| BSMNG | Quantity Ordered Against this Purchase Requisition | BSMNG | QUAN | 13(3) | MENG13 | ||||
| EBAKZ | Purchase Requisition Closed | EBAKZ | CHAR | 1 | XFELD | ||||
| SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | T148 | SOBKZ | |||
| MNG02 | Committed Quantity | MNG06 | QUAN | 13(3) | MENGV13 | ||||
| ERDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
| DAT01 | Committed Date | DAT05 | DATS | 8 | DATUM | ||||
| BADAT | Requisition (Request) Date | BADAT | DATS | 8 | DATUM | ||||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | T024 | EKGRP | EKG | ||
| TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| BSART | Purchase Requisition Document Type | BBSRT | CHAR | 4 | T161 | BSART | BBA | ||
| UMSOK | Special Stock Indicator for Physical Stock Transfer | UMSOK | CHAR | 1 | Assigned to domain | SOBKZ | |||
| RESLO | Issuing Storage Location for Stock Transport Order | RESLO | CHAR | 4 | Assigned to domain | LGORT | |||
| PRREG | Checking Rule for Availability Check | PRREG | CHAR | 2 | Assigned to domain | PRREG | PRR |
| Key field | Non-key field |
How do I retrieve data from SAP structure RPREQ using ABAP code?
As RPREQ 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 RPREQ as there is no data to select.How to access SAP table RPREQ
Within an ECC or HANA version of SAP you can also view further information about RPREQ 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