BAPIADURI SAP (BAPI Structure for URI Addresses (Business Address Services)) Structure details
Description: BAPI Structure for URI Addresses (Business Address Services)
Structure field list including key, data, relationships and ABAP select examples
BAPIADURI 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 "BAPI Structure for URI Addresses (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_BAPIADURI TYPE BAPIADURI.
The BAPIADURI table consists of various fields, each holding specific information or linking keys about BAPI Structure for URI Addresses (Business Address Services) data available in SAP. These include URI_TYPE (URI type flag), URI (URI, e.g. Homepage or ftp Address), STD_RECIP (Flag: Recipient is standard recipient for this number), 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 BAPIADURI 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 |
| STD_NO | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| URI_TYPE | URI type flag | AD_URITYPE | CHAR | 3 | AD_URITYPE | ||||
| URI | URI, e.g. Homepage or ftp Address | AD_URISCR | CHAR | 132 | AD_URISCR | ||||
| STD_RECIP | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| HOME_FLAG | Recipient address in this communication type (mail sys.grp) | AD_FLGHOME | CHAR | 1 | XFELD | ||||
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| URI_PART1 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART2 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART3 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART4 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART5 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART6 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART7 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART8 | Universal Resource Identifier (URI): Parts 1-8 | AD_URI_1 | CHAR | 250 | AD_URI_1 | ||||
| URI_PART9 | Universal Resource Identifier (URI) - Part 9 | AD_URI_9 | CHAR | 48 | TEXT48 | ||||
| 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 BAPIADURI using ABAP code?
As BAPIADURI 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 BAPIADURI as there is no data to select.How to access SAP table BAPIADURI
Within an ECC or HANA version of SAP you can also view further information about BAPIADURI 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