BCSS_COMM SAP (Communication Data) Structure details
Dictionary Type: Structure
Description: Communication Data
Description: Communication Data
Structure field list including key, data, relationships and ABAP select examples
BCSS_COMM 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 "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_BCSS_COMM TYPE BCSS_COMM.
The BCSS_COMM table consists of various fields, each holding specific information or linking keys about Communication Data data available in SAP. These include CONSNUMBER (Sequence Number), COUNTRY (Country for telephone/fax number), FLGDEFAULT (Standard Sender Address in this Communication Type), FLG_NOUSE (Flag: This Communication Number is Not Used).. 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 BCSS_COMM 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 |
| FAX | 0 | ||||||||
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | LAND1 | LND | |||
| 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 | ||||
| FAX_NUMBER | Fax number: dialling code+number | AD_FXNMBR | CHAR | 30 | CHAR30 | ||||
| FAX_EXTENS | Fax no.: Extension | AD_FXXTNS | CHAR | 10 | CHAR10 | ||||
| FAXNR_LONG | Complete number: dialling code+number+extension | AD_FXNRLNG | CHAR | 30 | CHAR30 | ||||
| FAXNR_CALL | Fax number for finding sender | AD_FAXNRCL | CHAR | 30 | CHAR30 | ||||
| FAX_GROUP | Fax group (G3, G4, ...) | AD_FXGRP | CHAR | 1 | AD_FXGRP | ||||
| DFT_RECEIV | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| R3_USER | Flag: Connected to an SAP System | AD_R3_USER | 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 | ||||
| SMTP | 0 | ||||||||
| 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 | ||||
| SMTP_ADDR | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| SMTP_SRCH | E-Mail Address Search Field | AD_SMTPAD2 | CHAR | 20 | CHAR20 | ||||
| DFT_RECEIV | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| R3_USER | Flag: Connected to an SAP System | AD_R3_USER | CHAR | 1 | XFELD | ||||
| ENCODE | Desired Data Coding (E-Mail) | AD_ENCODE | CHAR | 1 | AD_ENCODE | ||||
| TNEF | Flag: Receiver can receive TNEF coding via SMTP | AD_TNEF6 | 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 | ||||
| TEL | 0 | ||||||||
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | LAND1 | LND | |||
| 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 | ||||
| TEL_NUMBER | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| TEL_EXTENS | Telephone no.: Extension | AD_TLXTNS | CHAR | 10 | CHAR10 | ||||
| TELNR_LONG | Complete number: dialling code+number+extension | AD_TELNRLG | CHAR | 30 | CHAR30 | ||||
| TELNR_CALL | Telephone number for determining caller | AD_TELNRCL | CHAR | 30 | CHAR30 | ||||
| DFT_RECEIV | Indicator: Telephone is SMS-Enabled | AD_FLGSMS | CHAR | 1 | AD_FLGSMS | ||||
| R3_USER | Indicator: Telephone is a Mobile Telephone | AD_FLGMOB | CHAR | 1 | AD_FLGMOB | ||||
| 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 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BCSS_COMM using ABAP code?
As BCSS_COMM 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 BCSS_COMM as there is no data to select.How to access SAP table BCSS_COMM
Within an ECC or HANA version of SAP you can also view further information about BCSS_COMM 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