BUP_S_COMMDATA_READ_API SAP (BP-API: Read Communication Data) Structure details
Description: BP-API: Read Communication Data
Related tables to BUP_S_COMMDATA_READ_API
Access table BUP_S_COMMDATA_READ_API
Structure field list including key, data, relationships and ABAP select examples
BUP_S_COMMDATA_READ_API 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 "BP-API: Read Communication 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_BUP_S_COMMDATA_READ_API TYPE BUP_S_COMMDATA_READ_API.
The BUP_S_COMMDATA_READ_API table consists of various fields, each holding specific information or linking keys about BP-API: Read Communication Data data available in SAP. These include FACSIMILE (Indicator: Read this communication type), EMAIL (Indicator: Read this communication type), WEB (Indicator: Read this communication type), TELEX (Indicator: Read this communication type).. 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 BUP_S_COMMDATA_READ_API 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 |
| TELEPHONE | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| FACSIMILE | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | |||||
| WEB | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| TELEX | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| TELETEX | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| RML | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| X400 | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| PRINTER | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| SSF | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD | ||||
| PAGER | Indicator: Read this communication type | ADDR_READ_COMMUNICATION_TYPE | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BUP_S_COMMDATA_READ_API using ABAP code?
As BUP_S_COMMDATA_READ_API 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 BUP_S_COMMDATA_READ_API as there is no data to select.How to access SAP table BUP_S_COMMDATA_READ_API
Within an ECC or HANA version of SAP you can also view further information about BUP_S_COMMDATA_READ_API 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