BAPIBUS1006_ADPAG SAP (BP: Address Data - Pager) Structure details
Description: BP: Address Data - Pager
Related tables to BAPIBUS1006_ADPAG
Access table BAPIBUS1006_ADPAG
Structure field list including key, data, relationships and ABAP select examples
BAPIBUS1006_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 "BP: Address Data - Pager" 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_BAPIBUS1006_ADPAG TYPE BAPIBUS1006_ADPAG.
The BAPIBUS1006_ADPAG table consists of various fields, each holding specific information or linking keys about BP: Address Data - Pager data available in SAP. These include COUNTRY (Country for telephone/fax number), COUNTRYISO (Country ISO code), STD_NO (Standard Sender Address in this Communication Type), PAGER_TYPE (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: Cannot Be Enhanced
SAP BAPIBUS1006_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 |
ADDRESS_GUID | UUID in character form | SYSUUID_C | CHAR | 32 | SYSUUID_C | ||||
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 | ||||
PAGER_TYPE | Pager Service | AD_PAGSERV | CHAR | 4 | TSAPD | CHAR4 | |||
PAGER | Pager number | AD_PAGNMBR | CHAR | 30 | TEXT30 | ||||
PAGER_NO | Normalized pager search field | AD_PGNRLNG | CHAR | 30 | CHAR30 | ||||
CALLER_NO | Pager number for finding sender | AD_PAGNRCL | CHAR | 30 | CHAR30 | ||||
STD_RECIP | Encoded Reference to a Sequence Number | AD_CONSREF | CHAR | 1 | AD_CONSREF | ||||
R_3_USER | Encoded Reference to a Sequence Number | AD_CONSREF | CHAR | 1 | AD_CONSREF | ||||
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 | ||||
VALID_FROM | Communication Data: Valid From (YYYYMMDDHHMMSS) | AD_VALFROM | CHAR | 14 | TIMESTMP | ||||
VALID_TO | Communication Data: Valid To (YYYYMMDDHHMMSS) | AD_VALTO | CHAR | 14 | TIMESTAMP |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPIBUS1006_ADPAG using ABAP code?
As BAPIBUS1006_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 BAPIBUS1006_ADPAG as there is no data to select.How to access SAP table BAPIBUS1006_ADPAG
Within an ECC or HANA version of SAP you can also view further information about BAPIBUS1006_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