RM06CUMS_S SAP (RM06CUMS Output structure) Structure details
Description: RM06CUMS Output structure
Structure field list including key, data, relationships and ABAP select examples
RM06CUMS_S 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 "RM06CUMS Output structure" 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_RM06CUMS_S TYPE RM06CUMS_S.
The RM06CUMS_S table consists of various fields, each holding specific information or linking keys about RM06CUMS Output structure data available in SAP. These include EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), EKORG (Purchasing Organization), EKGRP (Purchasing Group).. 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: Cannot Be Enhanced
SAP RM06CUMS_S 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 |
ICON | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
EKGRP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
WEBRE | Indicator: GR-Based Invoice Verification | WEBRE | CHAR | 1 | XFELD | ||||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
MAKTX | Material Description (Short Text) | MAKTX | CHAR | 40 | TEXT40 | ||||
MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
DISPO | MRP Controller (Materials Planner) | DISPO | CHAR | 3 | Assigned to domain | DISPO | DGR | HS_T024D | |
NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
PSTLZ | Postal Code | PSTLZ | CHAR | 10 | PSTLZ | ||||
ORT01 | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
CUM_SA | Cumulative Qty Received for SchedAgr | /SPE/INB_CUM_SA | QUAN | 15(3) | MENG15 | ||||
ABFTZ_OLD | Original Agreed Cumulative Quantity | /SPE/CQ_ABFTZ_OLD | QUAN | 13(3) | MENG13 | ||||
ABDAT_OLD | Original Reconciliation Date for the Agreed Cumulative Qty | /SPE/CQ_ABDAT_OLD | DATS | 8 | DATUM | ||||
ABFTZ | Agreed Cumulative Quantity | ABFTZ | QUAN | 13(3) | MENG13 | ||||
ABDAT | Reconciliation Date for Agreed Cumulative Quantity | ABDAT | DATS | 8 | DATUM | ||||
SPE_CQ_CTRLTYPE | CQ Control Type | /SPE/CQ_CONTROL_TYPE | CHAR | 1 | /SPE/CQ_CONTROL_TYPE | ||||
SPE_CQ_NOCQ | No Transmission of Cumulative Quantities in SA Release | /SPE/CQ_NOCQ | CHAR | 1 | XFELD | ||||
STATUS | Status | /SPE/CQ_ME88_STATUS | CHAR | 60 | TEXT60 |
Key field | Non-key field |
How do I retrieve data from SAP structure RM06CUMS_S using ABAP code?
As RM06CUMS_S 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 RM06CUMS_S as there is no data to select.How to access SAP table RM06CUMS_S
Within an ECC or HANA version of SAP you can also view further information about RM06CUMS_S 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