TE809D SAP (Interface MRU meter reading unit) Structure details
Description: Interface MRU meter reading unit
Structure field list including key, data, relationships and ABAP select examples
TE809D 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 "Interface MRU meter reading unit" 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_TE809D TYPE TE809D.
The TE809D table consists of various fields, each holding specific information or linking keys about Interface MRU meter reading unit data available in SAP. These include AB (Date from which time slice is valid), BIS (Date at Which a Time Slice Expires), ABLEINH (Meter reading unit (old value)), MRU_NEW (Meter reading unit (new value)).. 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 (character-type)
SAP TE809D 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 |
| ANLAGE | Installation | ANLAGE | CHAR | 10 | EANL | ALPHA | ANLAGE | ANL | EANL |
| AB | Date from which time slice is valid | ABZEITSCH | DATS | 8 | DATUM | ||||
| BIS | Date at Which a Time Slice Expires | BISZEITSCH | DATS | 8 | DATUM | ||||
| ABLEINH | Meter reading unit (old value) | ABLEALT | CHAR | 8 | TE422 | ABLEINHEIT | |||
| MRU_NEW | Meter reading unit (new value) | ABLENEU | CHAR | 8 | TE422 | ABLEINHEIT | |||
| MRU_REG | Meter reading unit (from regional structure) | ABLEREG | CHAR | 8 | TE422 | ABLEINHEIT | |||
| SPARTE | Division | SPARTE | CHAR | 2 | TSPA | SPART | SPA | ||
| AKLASSE | Billing class | AKLASSE | CHAR | 4 | EAKLASSE | AKLASSE | AKL | ||
| XMRORDER | Indicator: meter reading order exists for installation | E_XMRORDER | CHAR | 1 | XFIELD | ||||
| PORTION | Portion | PORTION | CHAR | 8 | TE420 | PORTION | TPR | E420 | |
| XCONTRACTS | Several contracts allocated to installation | E_XCONTRACTS | CHAR | 1 | XFIELD | ||||
| VERTRAG | Contract | VERTRAG | CHAR | 10 | EVER | ALPHA | VERTRAG | VTG | EVER |
| PORTIONABW | Alternative portion | PORTIONABW | CHAR | 8 | TE420 | PORTION | TKY | ||
| PYPLT | Payment plan type | E_PYPLT | CHAR | 4 | TE015 | E_PYPLT | PYPT | ||
| EINZDAT | Move-In Date | EINZDAT | DATS | 8 | DATUM | ||||
| AUSZDAT | Move-Out Date | AUSZDAT | DATS | 8 | DATUM | ||||
| VSTELLE | Premise | VSTELLE | CHAR | 10 | EVBS | ALPHA | VSTELLE | VBS | EVBS |
| HAUS | Connection Object | HAUS | CHAR | 30 | IFLOT | TPLNR | TPLNR | HAU | EHAU |
| ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | ADRC | ALPHA | AD_ADDRNUM | ADR | |
| COUNTRY | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
| CITY_CODE | City code for city/street file | AD_CITYNUM | CHAR | 12 | ADRCITY | ALPHA | CITY_CODE | ||
| STREETCODE | Street Number for City/Street File | AD_STRNUM | CHAR | 12 | ADRSTREET | ALPHA | STRT_CODE | ||
| HOUSE_NUM | House number (numerical part) | HOUSENUM | NUMC | 10 | NUMC10 | ||||
| HOUSE_SUPP | House number affix | HSN_SUPP | CHAR | 4 | TEXT4 | ||||
| ADRESSLINE | Address line | ADRESSLINE | CHAR | 80 | LINES |
| Key field | Non-key field |
How do I retrieve data from SAP structure TE809D using ABAP code?
As TE809D 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 TE809D as there is no data to select.How to access SAP table TE809D
Within an ECC or HANA version of SAP you can also view further information about TE809D 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