MMPUR_PR_EXT_REL_SEND SAP (Data of Purchase Requisition Item To Be Sent) Structure details
Description: Data of Purchase Requisition Item To Be Sent
Related tables to MMPUR_PR_EXT_REL_SEND
Access table MMPUR_PR_EXT_REL_SEND
Structure field list including key, data, relationships and ABAP select examples
MMPUR_PR_EXT_REL_SEND 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 "Data of Purchase Requisition Item To Be Sent" 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_MMPUR_PR_EXT_REL_SEND TYPE MMPUR_PR_EXT_REL_SEND.
The MMPUR_PR_EXT_REL_SEND table consists of various fields, each holding specific information or linking keys about Data of Purchase Requisition Item To Be Sent data available in SAP. These include AKTYP (Transaction type), TESTRUN (Boolean type), HOLD_COMPLETE (Indicator for Posting of a Requisition), HOLD_UNCOMPLETE (Indicator for Posting of a Requisition).. 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 MMPUR_PR_EXT_REL_SEND 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 |
| PR_HEADER | 0 | ||||||||
| AKTYP | Transaction type | TRTYP | CHAR | 1 | TRTYP | ||||
| TESTRUN | Boolean type | MMPUR_BOOL | CHAR | 1 | CHAR1 | ||||
| HOLD_COMPLETE | Indicator for Posting of a Requisition | BAPIMEREQPOSTFLAG | CHAR | 1 | BAPIMEREQPOSTFLAG | ||||
| HOLD_UNCOMPLETE | Indicator for Posting of a Requisition | BAPIMEREQPOSTFLAG | CHAR | 1 | BAPIMEREQPOSTFLAG | ||||
| PARK_COMPLETE | Indicator for Posting of a Requisition | BAPIMEREQPOSTFLAG | CHAR | 1 | BAPIMEREQPOSTFLAG | ||||
| PARK_UNCOMPLETE | Indicator for Posting of a Requisition | BAPIMEREQPOSTFLAG | CHAR | 1 | BAPIMEREQPOSTFLAG | ||||
| DATA | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| BANFN | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| BANFN_EXT | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| BSART | Order Type (Purchasing) | BSART | CHAR | 4 | BSART | BSA | |||
| BSAKZ | Control indicator for purchasing document type | BSAKZ | CHAR | 1 | BSAKZ | ||||
| BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
| GSFRG | Overall release of purchase requisitions | GSFRG | CHAR | 1 | XFELD | ||||
| ESTKZ | Creation Indicator (Purchase Requisition/Schedule Lines) | ESTKZ | CHAR | 1 | ESTKZ | ||||
| PINCR | Item Number Interval | PINCR | NUMC | 5 | PINCR | ||||
| LPONR | Last Item Number | LPONR | NUMC | 5 | EBELP | ||||
| KZZUO | Automatic Source Determination | KZZUO | CHAR | 1 | XFELD | ||||
| MEMORY | Purchase Requisition not yet Complete | MEMBF | CHAR | 1 | XFELD | ||||
| MEMORYTYPE | Category of Incompleteness | MEMORYTYPE | CHAR | 1 | MM_MEMORYTYPE | ||||
| DATAX | 0 | ||||||||
| BANFN | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| BANFN_EXT | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| BSART | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| BSAKZ | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| BSTYP | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| GSFRG | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| ESTKZ | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| PINCR | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| LPONR | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| KZZUO | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| MEMORY | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| MEMORYTYPE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| TEXT | 0 | ||||||||
| PR_ITEMS | 0 | ||||||||
| PR_ITEMS_TECH_DATA | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MMPUR_PR_EXT_REL_SEND using ABAP code?
As MMPUR_PR_EXT_REL_SEND 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 MMPUR_PR_EXT_REL_SEND as there is no data to select.How to access SAP table MMPUR_PR_EXT_REL_SEND
Within an ECC or HANA version of SAP you can also view further information about MMPUR_PR_EXT_REL_SEND 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