BAPIBUSISM007_ADTEL SAP (IS-M: BAPI Structure for Telephone Numbers (Bus.Add.Serv.)) Structure details
Description: IS-M: BAPI Structure for Telephone Numbers (Bus.Add.Serv.)
Related tables to BAPIBUSISM007_ADTEL
Access table BAPIBUSISM007_ADTEL
Structure field list including key, data, relationships and ABAP select examples
BAPIBUSISM007_ADTEL 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 "IS-M: BAPI Structure for Telephone Numbers (Bus.Add.Serv.)" 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_BAPIBUSISM007_ADTEL TYPE BAPIBUSISM007_ADTEL.
The BAPIBUSISM007_ADTEL table consists of various fields, each holding specific information or linking keys about IS-M: BAPI Structure for Telephone Numbers (Bus.Add.Serv.) data available in SAP. These include COUNTRYISO (Country ISO code), STD_NO (Standard Sender Address in this Communication Type), TELEPHONE (Telephone no.: dialling code+number), EXTENSION (Telephone no.: Extension).. 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 BAPIBUSISM007_ADTEL 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 |
| COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | T005 | LAND1 | LND | ||
| COUNTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| STD_NO | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| TELEPHONE | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| EXTENSION | Telephone no.: Extension | AD_TLXTNS | CHAR | 10 | CHAR10 | ||||
| TEL_NO | Complete number: dialling code+number+extension | AD_TELNRLG | CHAR | 30 | CHAR30 | ||||
| CALLER_NO | Telephone number for determining caller | AD_TELNRCL | CHAR | 30 | CHAR30 | ||||
| STD_RECIP | Indicator: Telephone is SMS-Enabled | AD_FLGSMS | CHAR | 1 | AD_FLGSMS | ||||
| R_3_USER | Indicator: Telephone is a Mobile Telephone | AD_FLGMOB | CHAR | 1 | AD_FLGMOB | ||||
| HOME_FLAG | Recipient address in this communication type (mail sys.grp) | AD_FLGHOME | CHAR | 1 | XFELD | ||||
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| ERRORFLAG | Flag: Record not processed | AD_ERRBAPI | CHAR | 1 | XFELD | ||||
| FLG_NOUSE | Flag: This Communication Number is Not Used | AD_FLNOUSE | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIBUSISM007_ADTEL using ABAP code?
As BAPIBUSISM007_ADTEL 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 BAPIBUSISM007_ADTEL as there is no data to select.How to access SAP table BAPIBUSISM007_ADTEL
Within an ECC or HANA version of SAP you can also view further information about BAPIBUSISM007_ADTEL 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