ADPAG SAP (Pager Number Transfer Structure (Business Address Services)) Structure details
Description: Pager Number Transfer Structure (Business Address Services)
Structure field list including key, data, relationships and ABAP select examples
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 "Pager Number Transfer Structure (Business Address Services)" 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_ADPAG TYPE ADPAG.
The ADPAG table consists of various fields, each holding specific information or linking keys about Pager Number Transfer Structure (Business Address Services) data available in SAP. These include COUNTRY (Country for telephone/fax number), FLGDEFAULT (Standard Sender Address in this Communication Type), FLG_NOUSE (Flag: This Communication Number is Not Used), HOME_FLAG (Recipient address in this communication type (mail sys.grp)).. 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 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 |
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 | ||||
PAGER_SERV | Pager Service | AD_PAGSERV | CHAR | 4 | TSAPD | CHAR4 | |||
PAGER_NMBR | Pager number | AD_PAGNMBR | CHAR | 30 | TEXT30 | ||||
PAGER_LONG | Normalized pager search field | AD_PGNRLNG | CHAR | 30 | CHAR30 | ||||
PAGER_CALL | Pager number for finding sender | AD_PAGNRCL | CHAR | 30 | CHAR30 | ||||
DFT_RECEIV | Encoded Reference to a Sequence Number | AD_CONSREF | CHAR | 1 | AD_CONSREF | ||||
R3_USER | Encoded Reference to a Sequence Number | AD_CONSREF | CHAR | 1 | AD_CONSREF | ||||
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 ADPAG using ABAP code?
As 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 ADPAG as there is no data to select.How to access SAP table ADPAG
Within an ECC or HANA version of SAP you can also view further information about 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