CMS_STR_ADDRESS_URI_640 SAP (CMS BUPA BadI: Structure for URI Address) Structure details
Description: CMS BUPA BadI: Structure for URI Address
Related tables to CMS_STR_ADDRESS_URI_640
Access table CMS_STR_ADDRESS_URI_640
Structure field list including key, data, relationships and ABAP select examples
CMS_STR_ADDRESS_URI_640 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 "CMS BUPA BadI: Structure for URI Address" 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_CMS_STR_ADDRESS_URI_640 TYPE CMS_STR_ADDRESS_URI_640.
The CMS_STR_ADDRESS_URI_640 table consists of various fields, each holding specific information or linking keys about CMS BUPA BadI: Structure for URI Address data available in SAP. These include FLGDEFAULT (Standard Sender Address in this Communication Type), FLG_NOUSE (Flag: This Communication Number is Not Used), HOME_FLAG (Recipient address in this communication type (mail sys.grp)), URI_TYPE (URI type flag).. 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 CMS_STR_ADDRESS_URI_640 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 |
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| FLGDEFAULT | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| FLG_NOUSE | Flag: This Communication Number is Not Used | AD_FLNOUSE | CHAR | 1 | XFELD | ||||
| HOME_FLAG | Recipient address in this communication type (mail sys.grp) | AD_FLGHOME | CHAR | 1 | XFELD | ||||
| URI_TYPE | URI type flag | AD_URITYPE | CHAR | 3 | AD_URITYPE | ||||
| URI_SCREEN | URI, e.g. Homepage or ftp Address | AD_URISCR | CHAR | 132 | AD_URISCR | ||||
| DFT_RECEIV | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| REMARK | Communication link notes | AD_REMARK2 | CHAR | 50 | TEXT50 | ||||
| VALID_FROM | Communication Data: Valid From (YYYYMMDDHHMMSS) | AD_VALFROM | CHAR | 14 | TIMESTMP | ||||
| VALID_TO | Communication Data: Valid To (YYYYMMDDHHMMSS) | AD_VALTO | CHAR | 14 | TIMESTAMP | ||||
| UPDATEFLAG | Change operation code ('I'nsert, 'U'pdate, 'D'elete) | AD_OP_CODE | CHAR | 1 | AD_OP_CODE | ||||
| URI_ADDR | Universal Resource Identifier (URI) | AD_URI | LCHR | 2048 | AD_URI |
| Key field | Non-key field |
How do I retrieve data from SAP structure CMS_STR_ADDRESS_URI_640 using ABAP code?
As CMS_STR_ADDRESS_URI_640 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 CMS_STR_ADDRESS_URI_640 as there is no data to select.How to access SAP table CMS_STR_ADDRESS_URI_640
Within an ECC or HANA version of SAP you can also view further information about CMS_STR_ADDRESS_URI_640 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