ISU_MRDOC_RSLT_CRTE_MRDOC SAP (Create MeterReadingDocument Node) Structure details
Description: Create MeterReadingDocument Node
Related tables to ISU_MRDOC_RSLT_CRTE_MRDOC
Access table ISU_MRDOC_RSLT_CRTE_MRDOC
Structure field list including key, data, relationships and ABAP select examples
ISU_MRDOC_RSLT_CRTE_MRDOC 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 "Create MeterReadingDocument Node" 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_ISU_MRDOC_RSLT_CRTE_MRDOC TYPE ISU_MRDOC_RSLT_CRTE_MRDOC.
The ISU_MRDOC_RSLT_CRTE_MRDOC table consists of various fields, each holding specific information or linking keys about Create MeterReadingDocument Node data available in SAP. These include ID (Proxy Data Element (generated)), RESULT (), CONTROLLER (), METER_READING_DATE (Proxy Data Element (generated)).. 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 ISU_MRDOC_RSLT_CRTE_MRDOC 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 |
| CONTROLLER | 0 | ||||||||
| ID | Proxy Data Element (generated) | ISU_NOSC_METER_READINGDOCUMENT | CHAR | 20 | |||||
| RESULT | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| METER_READING_DATE | Proxy Data Element (generated) | ISU_DATE1 | DATS | 8 | XSDDATE_D | ||||
| METER_READING_TIME | Proxy Data Element (generated) | ISU_TIME | TIMS | 6 | XSDTIME_T | ||||
| MAXIMIUM_METER_READING_DATE | Proxy Data Element (generated) | ISU_DATE1 | DATS | 8 | XSDDATE_D | ||||
| MAXIMIUM_METER_READING_TIME | Proxy Data Element (generated) | ISU_TIME | TIMS | 6 | XSDTIME_T | ||||
| METER_READING_TYPE_CODE | Proxy Data Element (generated) | ISU_NOSC_METERREADINGTYPE_CODE | CHAR | 2 | |||||
| METER_READING_RESULT_VALUE | Proxy Data Element (generated) | ISU_METER_READING_RESULT_VALUE | DEC | 25(10) | |||||
| METER_READER_NOTE_CODE | Proxy Data Element (generated) | ISU_NOSC_METERREADER_NOTE_CODE | CHAR | 4 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ISU_MRDOC_RSLT_CRTE_MRDOC using ABAP code?
As ISU_MRDOC_RSLT_CRTE_MRDOC 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 ISU_MRDOC_RSLT_CRTE_MRDOC as there is no data to select.How to access SAP table ISU_MRDOC_RSLT_CRTE_MRDOC
Within an ECC or HANA version of SAP you can also view further information about ISU_MRDOC_RSLT_CRTE_MRDOC 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