BUS0ADTEL SAP (CBP: Telephone data (transfer structure)) Structure details
Description: CBP: Telephone data (transfer structure)
Structure field list including key, data, relationships and ABAP select examples
BUS0ADTEL 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 "CBP: Telephone data (transfer structure)" 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_BUS0ADTEL TYPE BUS0ADTEL.
The BUS0ADTEL table consists of various fields, each holding specific information or linking keys about CBP: Telephone data (transfer structure) data available in SAP. These include ADDRNUMBER (Address number), CONSNUMBER (Sequence Number), COUNTRY (Country for telephone/fax number), FLGDEFAULT (Standard Sender Address in 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: Not classified
SAP BUS0ADTEL 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 |
PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | T005 | 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 BUS0ADTEL using ABAP code?
As BUS0ADTEL 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 BUS0ADTEL as there is no data to select.How to access SAP table BUS0ADTEL
Within an ECC or HANA version of SAP you can also view further information about BUS0ADTEL 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