CNMMDATES_EKBE SAP (Scheduling Structure for Project-Oriented MM: PO History) Structure details
Description: Scheduling Structure for Project-Oriented MM: PO History
Related tables to CNMMDATES_EKBE
Access table CNMMDATES_EKBE
Structure field list including key, data, relationships and ABAP select examples
CNMMDATES_EKBE 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 "Scheduling Structure for Project-Oriented MM: PO History" 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_CNMMDATES_EKBE TYPE CNMMDATES_EKBE.
The CNMMDATES_EKBE table consists of various fields, each holding specific information or linking keys about Scheduling Structure for Project-Oriented MM: PO History data available in SAP. These include RSPOS (Item Number of Reservation/Dependent Requirement), RSART (Record type), ICONS (30 Characters), DTER (Requirement Date for the Component).. 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: Not classified
SAP CNMMDATES_EKBE 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 |
| RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
| RSPOS | Item Number of Reservation/Dependent Requirement | RSPOS | NUMC | 4 | RSPOS | RPO | |||
| RSART | Record type | RSART | CHAR | 1 | RSART | ||||
| ICONS | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
| DTER | Requirement Date for the Component | BDTER | DATS | 8 | DATUM | ||||
| KWBDTER | Requirements Date of a Component in Calendar Weeks | KWBDTER | CHAR | 7 | CHAR7 | ||||
| EBELN | Purchase Order Number | BSTNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | |
| EBELP | Purchase Order Item Number | BSTPO | NUMC | 5 | Assigned to domain | EBELP | |||
| XEKET | Indicator That Schedule Lines Exist | CNMM_XEKET | CHAR | 1 | XFELD | ||||
| XEKES | Indicator that confirmations exist | CNMM_XEKES | CHAR | 1 | XFELD | ||||
| XEKBE | Indicator that the purchase order history exists | CNMM_XEKBE | CHAR | 1 | XFELD | ||||
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| KWBUDAT | Posting Date for Material Document in Calendar Weeks | KWBUDAT_MSEG | CHAR | 7 | CHAR7 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CNMMDATES_EKBE using ABAP code?
As CNMMDATES_EKBE 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 CNMMDATES_EKBE as there is no data to select.How to access SAP table CNMMDATES_EKBE
Within an ECC or HANA version of SAP you can also view further information about CNMMDATES_EKBE 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