/BOFU/ADDRS_REMOTE_MAIL_ADDR SAP (RML Address Data) Structure details
Description: RML Address Data
Related tables to /BOFU/ADDRS_REMOTE_MAIL_ADDR
Access table /BOFU/ADDRS_REMOTE_MAIL_ADDR
Structure field list including key, data, relationships and ABAP select examples
/BOFU/ADDRS_REMOTE_MAIL_ADDR 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 "RML Address Data" 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_/BOFU/ADDRS_REMOTE_MAIL_ADDR TYPE /BOFU/ADDRS_REMOTE_MAIL_ADDR.
The /BOFU/ADDRS_REMOTE_MAIL_ADDR table consists of various fields, each holding specific information or linking keys about RML Address Data data available in SAP. These include FLG_NOUSE (Flag: This Communication Number is Not Used), SYMB_DEST (Symbolic destination), RECVR_TYPE (Recipient type (not currently used)), UMAND (RML- Client (Remote Mail, SAP - SAP - Communication)).. 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 /BOFU/ADDRS_REMOTE_MAIL_ADDR 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 |
RML_ID | Node ID as in eSOA Model | /BOFU/ADDR_NODE_ID | CHAR | 70 | /BOFU/ADDR_NODE_ID | ||||
FLG_NOUSE | Flag: This Communication Number is Not Used | AD_FLNOUSE | CHAR | 1 | XFELD | ||||
SYMB_DEST | Symbolic destination | AD_SYMBDST | CHAR | 10 | CHAR10 | ||||
RECVR_TYPE | Recipient type (not currently used) | AD_RCVRTYP | CHAR | 1 | CHAR1 | ||||
UMAND | RML- Client (Remote Mail, SAP - SAP - Communication) | AD_UMAND | CHAR | 3 | CHAR3 | ||||
UNAME | RML Name (Remote Mail, SAP - SAP - Communication) | AD_UNAME | CHAR | 12 | CHAR12 | ||||
VALID_FROM | Communication Data: Valid From (YYYYMMDDHHMMSS) | AD_VALFROM | CHAR | 14 | TIMESTMP | ||||
VALID_TO | Communication Data: Valid To (YYYYMMDDHHMMSS) | AD_VALTO | CHAR | 14 | TIMESTAMP | ||||
CHANGED_FIELDS | 0 | ||||||||
NOTES | 0 | ||||||||
USAGES | 0 | ||||||||
UPDATEFLAG | Change operation code ('I'nsert, 'U'pdate, 'D'elete) | AD_OP_CODE | CHAR | 1 | AD_OP_CODE |
Key field | Non-key field |
How do I retrieve data from SAP structure /BOFU/ADDRS_REMOTE_MAIL_ADDR using ABAP code?
As /BOFU/ADDRS_REMOTE_MAIL_ADDR 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 /BOFU/ADDRS_REMOTE_MAIL_ADDR as there is no data to select.How to access SAP table /BOFU/ADDRS_REMOTE_MAIL_ADDR
Within an ECC or HANA version of SAP you can also view further information about /BOFU/ADDRS_REMOTE_MAIL_ADDR 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