FVD_PHYSICAL_ADDRESS SAP (Proxy Structure (generated)) Structure details
Description: Proxy Structure (generated)
Related tables to FVD_PHYSICAL_ADDRESS
Access table FVD_PHYSICAL_ADDRESS
Structure field list including key, data, relationships and ABAP select examples
FVD_PHYSICAL_ADDRESS 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 "Proxy Structure (generated)" 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_FVD_PHYSICAL_ADDRESS TYPE FVD_PHYSICAL_ADDRESS.
The FVD_PHYSICAL_ADDRESS table consists of various fields, each holding specific information or linking keys about Proxy Structure (generated) data available in SAP. These include COUNTRY_CODE (Proxy Datenelement (generiert)), COUNTRY_NAME (), CONTROLLER (), LANGUAGE_CODE (Proxy Datenelement (generiert)).. 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 (Deep)
SAP FVD_PHYSICAL_ADDRESS 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 |
| CONTROLLER | 0 | ||||||||
| COUNTRY_CODE | Proxy Datenelement (generiert) | FVD_COUNTRY_CODE | CHAR | 3 | |||||
| COUNTRY_NAME | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LANGUAGE_CODE | Proxy Datenelement (generiert) | FVD_LANGUAGE_CODE | CHAR | 9 | |||||
| CONTENT | Proxy Data Element (generated) | FVD_MEDIUM_NAME_CONTENT | CHAR | 40 | |||||
| REGION_CODE | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LIST_ID | 0 | ||||||||
| LIST_VERSION_ID | 0 | ||||||||
| LIST_AGENCY_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_AGENCY_ID | An AgencyIdentificationCode is a code representation of the | FVD_AGENCY_IDENTIFICATION_CODE | CHAR | 3 | |||||
| CONTENT | 0 | ||||||||
| REGION_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| STREET_POSTAL_CODE | Proxy Data Element (generated) | FVD_POSTAL_CODE | CHAR | 10 | |||||
| POBOX_POSTAL_CODE | Proxy Data Element (generated) | FVD_POSTAL_CODE | CHAR | 10 | |||||
| COMPANY_POSTAL_CODE | Proxy Data Element (generated) | FVD_POSTAL_CODE | CHAR | 10 | |||||
| CITY_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| ADDITIONAL_CITY_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| DISTRICT_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| POBOX_ID | Proxy Data Element (generated) | FVD_POBOX_ID | CHAR | 10 | |||||
| POBOX_INDICATOR | 'Indicator' is the binary coded specification of a fact | FVD_INDICATOR | CHAR | 5 | |||||
| POBOX_COUNTRY_CODE | Proxy Datenelement (generiert) | FVD_COUNTRY_CODE | CHAR | 3 | |||||
| POBOX_COUNTRY_NAME | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LANGUAGE_CODE | Proxy Datenelement (generiert) | FVD_LANGUAGE_CODE | CHAR | 9 | |||||
| CONTENT | Proxy Data Element (generated) | FVD_MEDIUM_NAME_CONTENT | CHAR | 40 | |||||
| POBOX_REGION_CODE | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LIST_ID | 0 | ||||||||
| LIST_VERSION_ID | 0 | ||||||||
| LIST_AGENCY_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_AGENCY_ID | An AgencyIdentificationCode is a code representation of the | FVD_AGENCY_IDENTIFICATION_CODE | CHAR | 3 | |||||
| CONTENT | 0 | ||||||||
| POBOX_REGION_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| POBOX_CITY_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| STREET_NAME | Proxy Data Element (generated) | FVD_STREET_NAME | CHAR | 60 | |||||
| STREET_PREFIX_NAME | 0 | ||||||||
| STREET_SUFFIX_NAME | 0 | ||||||||
| HOUSE_ID | Proxy Data Element (generated) | FVD_HOUSE_ID3 | CHAR | 10 | |||||
| ADDITIONAL_HOUSE_ID | Proxy Data Element (generated) | FVD_HOUSE_ID3 | CHAR | 10 | |||||
| BUILDING_ID | Proxy Data Element (generated) | FVD_BUILDING_ID | CHAR | 10 | |||||
| FLOOR_ID | Proxy Data Element (generated) | FVD_FLOOR_ID3 | CHAR | 10 | |||||
| ROOM_ID | Proxy Data Element (generated) | FVD_ROOM_ID | CHAR | 10 | |||||
| CARE_OF_NAME | Proxy Data Element (generated) | FVD_PERSON_NAME_MIDDLE_NAM_TAB | CHAR | 40 | |||||
| DESCRIPTION | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure FVD_PHYSICAL_ADDRESS using ABAP code?
As FVD_PHYSICAL_ADDRESS 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 FVD_PHYSICAL_ADDRESS as there is no data to select.How to access SAP table FVD_PHYSICAL_ADDRESS
Within an ECC or HANA version of SAP you can also view further information about FVD_PHYSICAL_ADDRESS 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