BAPIAD3VL SAP (Address type 3 distribution BAPI structure) Structure details
Description: Address type 3 distribution BAPI structure
Structure field list including key, data, relationships and ABAP select examples
BAPIAD3VL 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 "Address type 3 distribution BAPI structure" 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_BAPIAD3VL TYPE BAPIAD3VL.
The BAPIAD3VL table consists of various fields, each holding specific information or linking keys about Address type 3 distribution BAPI structure data available in SAP. These include FROM_DATE (Valid-from date - in current Release only 00010101 possible), TO_DATE (Valid-to date in current Release only 99991231 possible), TITLE_P (Form-of-Address Key), FIRSTNAME (First name).. 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 BAPIAD3VL 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 |
| ADDR_VERS | Version ID for International Addresses | AD_NATION | CHAR | 1 | TSADV | AD_NATION | ADDRESS_NATION | ||
| FROM_DATE | Valid-from date - in current Release only 00010101 possible | AD_DATE_FR | DATS | 8 | DATUM | ||||
| TO_DATE | Valid-to date in current Release only 99991231 possible | AD_DATE_TO | DATS | 8 | DATUM | ||||
| TITLE_P | Form-of-Address Key | AD_TITLE | CHAR | 4 | TSAD3 | AD_TITLE | |||
| FIRSTNAME | First name | AD_NAMEFIR | CHAR | 40 | TEXT40 | ||||
| LASTNAME | Last name | AD_NAMELAS | CHAR | 40 | TEXT40 | ||||
| BIRTH_NAME | Name of person at birth | AD_NAME2_P | CHAR | 40 | TEXT40 | ||||
| MIDDLENAME | Middle name or second forename of a person | AD_NAMEMID | CHAR | 40 | TEXT40 | ||||
| SECONDNAME | Second surname of a person | AD_NAMLAS2 | CHAR | 40 | TEXT40 | ||||
| FULLNAME | Full Name of Person | AD_NAMTEXT | CHAR | 80 | TEXT80 | ||||
| FULLNAME_X | Status of Field 'Full Name' NAME_TEXT | AD_NAMCONV | CHAR | 1 | AD_NAMCONV | ||||
| TITLE_ACA1 | Academic Title: Key | AD_TITLE1 | CHAR | 4 | TSAD2 | AD_TITLE1 | AD_TITLE1 | ||
| TITLE_ACA2 | Second academic title (key) | AD_TITLE2 | CHAR | 4 | TSAD2 | AD_TITLE1 | |||
| PREFIX1 | Name Prefix (Key) | AD_PREFIX | CHAR | 4 | TSAD4 | AD_PREFIX | |||
| PREFIX2 | 2nd name prefix (key) | AD_PREFIX2 | CHAR | 4 | TSAD4 | AD_PREFIX | |||
| TITLE_SPPL | Name supplement, e.g. noble title (key) | AD_TITLES | CHAR | 4 | TSAD5 | AD_TITLES | |||
| NICKNAME | Nickname or name used | AD_NICKNAM | CHAR | 40 | TEXT40 | ||||
| INITIALS | 'Middle Initial' or personal initials | AD_INITS | CHAR | 10 | CHAR10 | ||||
| NAMEFORMAT | Name format | AD_FORMAT | CHAR | 2 | T005N | AD_NAMFORM | |||
| NAMCOUNTRY | Country for name format rule | AD_NAMCTRY | CHAR | 3 | T005 | LAND1 | |||
| NAMCTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| PROFESSION | Profession | AD_PROFESS | CHAR | 40 | TEXT40 | ||||
| SEX | Gender key | AD_SEX | CHAR | 1 | AD_SEX | ||||
| LANGU_P | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| LANGUP_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| SORT1_P | Search Term 1 | AD_SORT1 | CHAR | 20 | CHAR20 | ||||
| SORT2_P | Search Term 2 | AD_SORT2 | CHAR | 20 | CHAR20 | ||||
| LANGU_CR_P | Address record creation original language | AD_LANGUCR | LANG | 1 | T002 | ISOLA | SPRAS | ||
| LANGUCPISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| DEPARTMENT | Department | AD_DPRTMNT | CHAR | 40 | TEXT40 | ||||
| FUNCTION | Function | AD_FNCTN | CHAR | 40 | TEXT40 | ||||
| BUILDING_P | Building (number or code) | AD_BLDNG_P | CHAR | 10 | TEXT10 | ||||
| FLOOR_P | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOM_NO_P | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| INITS_SIG | Short name for correspondence | AD_ID_CODE | CHAR | 10 | TEXT10 | ||||
| INHOUSE_ML | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
| COMM_TYPE | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | TSAC | AD_COMM | |||
| PERS_GROUP | Person Group (Key) (Business Address Services) | AD_GROUP_P | CHAR | 4 | TSAD8 | AD_GROUP_P |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIAD3VL using ABAP code?
As BAPIAD3VL 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 BAPIAD3VL as there is no data to select.How to access SAP table BAPIAD3VL
Within an ECC or HANA version of SAP you can also view further information about BAPIAD3VL 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