BSS_ADPAG SAP (Com. Interface: Structure PAGER_DATA) Structure details
Description: Com. Interface: Structure PAGER_DATA
Structure field list including key, data, relationships and ABAP select examples
BSS_ADPAG 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 "Com. Interface: Structure PAGER_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_BSS_ADPAG TYPE BSS_ADPAG.
The BSS_ADPAG table consists of various fields, each holding specific information or linking keys about Com. Interface: Structure PAGER_DATA data available in SAP. These include COUNTRY (R3A BP: Country for Telephone and Fax Number), COUNTRYISO (R3A BP: ISO Code of Country), STD_NO (R3A BP: Standard Sender Address in This Method of Communic.), PAGER_TYPE (R3A GP: Subtype for Pager Service).. 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: Can be enhanced (character-type)
SAP BSS_ADPAG 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 | R3A BP: Country for Telephone and Fax Number | GB_COMCTRY | CHAR | 3 | CHAR3 | ||||
COUNTRYISO | R3A BP: ISO Code of Country | GB_INTCA | CHAR | 2 | CHAR2 | ||||
STD_NO | R3A BP: Standard Sender Address in This Method of Communic. | GB_FLGDFNR | CHAR | 1 | CHAR1 | ||||
PAGER_TYPE | R3A GP: Subtype for Pager Service | GB_PAGSERV | CHAR | 4 | CHAR4 | ||||
PAGER | R3A GP: Pager Number | GB_PAGNMBR | CHAR | 30 | CHAR30 | ||||
PAGER_NO | R3A GP: Normalized Search Field for Pager | GB_PGNRLNG | CHAR | 30 | CHAR30 | ||||
CALLER_NO | R3A GP: Pager Number for Finding Sender | GB_PAGNRCL | CHAR | 30 | CHAR30 | ||||
STD_RECIP | R3A BP: Indic.: Recipient is Standard Recipient for this No. | GB_DFTRCNR | CHAR | 1 | CHAR1 | ||||
R_3_USER | R3A BP: Indicator: Connected to R/3 | GB_R3_USER | CHAR | 1 | CHAR1 | ||||
HOME_FLAG | R3A BP:Recipient Addr. in This Meth. of Comm (Mail Syst Grp) | GB_FLGHOME | CHAR | 1 | CHAR1 | ||||
CONSNUMBER | R3A BP: Sequence Number | GB_CONSNUM | NUMC | 3 | NUMC3 | ||||
ERRORFLAG | R3A BP: Indicator: Record not Processed | GB_ERRBAPI | CHAR | 1 | CHAR1 | ||||
FLG_NOUSE | R3A BP: Indicator: Do Not Use this Communication Number | GB_FLNOUSE | CHAR | 1 | CHAR1 | ||||
VALID_FROM | Valid from (YYYYMMDDHHMMSS) | GB_VALFROM | CHAR | 14 | TIMESTMP | ||||
VALID_TO | Valid to (YYYYMMDDHHMMSS) | GB_VALTO | CHAR | 14 | TIMESTMP |
Key field | Non-key field |
How do I retrieve data from SAP structure BSS_ADPAG using ABAP code?
As BSS_ADPAG 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 BSS_ADPAG as there is no data to select.How to access SAP table BSS_ADPAG
Within an ECC or HANA version of SAP you can also view further information about BSS_ADPAG 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