/SAPSRM/S_PDO_MDF_DO_RELEASES SAP (Meatdat table for releases) Structure details
Description: Meatdat table for releases
Related tables to /SAPSRM/S_PDO_MDF_DO_RELEASES
Access table /SAPSRM/S_PDO_MDF_DO_RELEASES
Structure field list including key, data, relationships and ABAP select examples
/SAPSRM/S_PDO_MDF_DO_RELEASES 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 "Meatdat table for releases" 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_/SAPSRM/S_PDO_MDF_DO_RELEASES TYPE /SAPSRM/S_PDO_MDF_DO_RELEASES.
The /SAPSRM/S_PDO_MDF_DO_RELEASES table consists of various fields, each holding specific information or linking keys about Meatdat table for releases data available in SAP. These include LOG_SYSTEM (Logical System of Logistics Backend), OBJECT_TYPE (CRM Item Object Type), GUID (Globally Unique identifier), HEADER (Globally Unique identifier).. 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 /SAPSRM/S_PDO_MDF_DO_RELEASES 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 |
| LOG_SYSTEM | Logical System of Logistics Backend | BE_LOG_SYSTEM | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| OBJECT_TYPE | CRM Item Object Type | CRMT_SWO_OBJTYP_PROCESS_ITM_DB | CHAR | 10 | Assigned to domain | CRM_OJ_NAME_PROCESS_ITEM | |||
| GUID | Globally Unique identifier | BBP_GUID | RAW | 16 | SYSUUID | ||||
| HEADER | Globally Unique identifier | BBP_GUID | RAW | 16 | SYSUUID | ||||
| PD_NUMBER | Follow-On Document Object ID in Back-End System | BE_OBJECT_ID | CHAR | 20 | BBP_BE_OBJECT_ID | ||||
| NUMBER_INT | Item Number | BBP_ITEM_NO | NUMC | 10 | CRM_ITEM_NO | ||||
| DESCRIPTION | Product Description | COMT_PRSHTEXTX | CHAR | 40 | PRSHTEXT40 | ||||
| CREATED_AT | Transaction Was Created at This Time | BBP_CR_CREATED_AT | DEC | 15 | TZNTSTMPS | ||||
| QUANTITY | Quantity in Order Unit | BBP_MNG | QUAN | 13(3) | MENG13 | ||||
| UNIT | Unit of Measurement | BBP_UNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| VALUE | Net Value | BBP_VALUE | CURR | 15(2) | WERT8 | ||||
| CURRENCY | Currency | BBP_CURRENCY | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| DELIV_DATE | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| PROC_ORG | Purchasing Organization Department Description | BBP_PURCH_ORG_SHORT | CHAR | 12 | TEXT12 | ||||
| PROC_ORG_NAME | Releasing Purchasing Org. | BBP_CALL_OFF_PURCH_ORG | CHAR | 50 | BU_TEXT50 | ||||
| PLANT | Distribution CRM -> ERP: Plant | BBP_R3_PLANT | CHAR | 4 | BBP_R3_PLANT | ||||
| LOCATION_ID | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| PLANT_NAME | Releasing Plant | BBP_CALL_OFF_PLANT | CHAR | 50 | BU_TEXT50 | ||||
| QUAN_CF_E | Quantity of Entered Confirmation | BBP_CF_QUANT_E | QUAN | 15(3) | MENG15 | ||||
| PD_DESCRIPTION | Transaction Description | CRMT_PROCESS_DESCRIPTION | CHAR | 40 | CRM_PROCESS_DESCRIPTION | ||||
| DOCUMENT_TYPE | Text, 40 Characters Long | TEXT40 | CHAR | 40 | TEXT40 | ||||
| DOCUMENT_STATUS | Object status | J_TXT30 | CHAR | 30 | TEXT30 | ||||
| CREATED_DATE | Local Date | SYSTDATLO | DATS | 8 | SYDATS | ||||
| EXLIN | Configurable Line Item Number | /SAPSRM/EXLIN | CHAR | 40 | /SAPSRM/EXLIN |
| Key field | Non-key field |
How do I retrieve data from SAP structure /SAPSRM/S_PDO_MDF_DO_RELEASES using ABAP code?
As /SAPSRM/S_PDO_MDF_DO_RELEASES 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 /SAPSRM/S_PDO_MDF_DO_RELEASES as there is no data to select.How to access SAP table /SAPSRM/S_PDO_MDF_DO_RELEASES
Within an ECC or HANA version of SAP you can also view further information about /SAPSRM/S_PDO_MDF_DO_RELEASES 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