MMPURUI_RELEASEDOC_STY SAP (Structure for Contract Release Order) Structure details
Description: Structure for Contract Release Order
Related tables to MMPURUI_RELEASEDOC_STY
Access table MMPURUI_RELEASEDOC_STY
Structure field list including key, data, relationships and ABAP select examples
MMPURUI_RELEASEDOC_STY 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 "Structure for Contract Release Order" 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_MMPURUI_RELEASEDOC_STY TYPE MMPURUI_RELEASEDOC_STY.
The MMPURUI_RELEASEDOC_STY table consists of various fields, each holding specific information or linking keys about Structure for Contract Release Order data available in SAP. These include ITEM (Item Number of Purchasing Document), MATERIAL (Material Number), MATERIAL_TXT (Short Text), MPN_MATERIAL (Material Number Corresponding to Manufacturer Part 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 (Deep)
SAP MMPURUI_RELEASEDOC_STY 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 |
CONTRACT | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
ITEM | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
MATERIAL | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
MATERIAL_TXT | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
MPN_MATERIAL | Material Number Corresponding to Manufacturer Part Number | EMATN | CHAR | 18 | Assigned to domain | MATN1 | MATNR | HTN | |
MPN_TXT | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
SUPPLIER | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
SUPPLIER_TXT | Name of Vendor or Supplying Plant | MMPURUI_SUPPLNAME_TY | CHAR | 35 | CHAR35 | ||||
STATUS | Text (20 Characters) | TEXT20 | CHAR | 20 | TEXT20 | ||||
CREATE_ON | Purchase Order Date | BEDAT | DATS | 8 | DATUM | ||||
CREATE_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
TYPE | Short Text of Document Type | MMPURUI_BSART_TEXT_TY | SSTR | 20 | STATUS_TEXT | ||||
VALID_FROM | Start of Validity Period | KDATB | DATS | 8 | DATUM | ||||
VALID_TO | End of Validity Period | KDATE | DATS | 8 | DATUM | ||||
TARGET_QTY | Target Quantity | KTMNG | QUAN | 13(3) | MENGE | ||||
TARGET_VAL | Target Value for Outline Agreement in Document Currency | DZWERT | CURR | 13(2) | WERT7 | ||||
UNIT | Purchase Order Unit of Measure | BSTME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
EKOTX | Description of Purchasing Organization | EKOTX | CHAR | 20 | TEXT20 | ||||
MATKL | Material Group | MATKL | CHAR | 9 | Assigned to domain | MATKL | MKL | S_WBWG | |
MATKL_TXT | Material Group Description | WGBEZ | CHAR | 20 | TEXT20 | ||||
PLANT | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | Assigned to domain | WERKS | |||
TYPE_KEY | Purchasing Document Type | ESART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
OPEN_TRGTQUANT | Open Target Quantity | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure MMPURUI_RELEASEDOC_STY using ABAP code?
As MMPURUI_RELEASEDOC_STY 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 MMPURUI_RELEASEDOC_STY as there is no data to select.How to access SAP table MMPURUI_RELEASEDOC_STY
Within an ECC or HANA version of SAP you can also view further information about MMPURUI_RELEASEDOC_STY 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