RTCO_PHYSICAL_ADDRESS_GDT SAP (Proxy Structure (generated)) Structure details
Description: Proxy Structure (generated)
Related tables to RTCO_PHYSICAL_ADDRESS_GDT
Access table RTCO_PHYSICAL_ADDRESS_GDT
Structure field list including key, data, relationships and ABAP select examples
RTCO_PHYSICAL_ADDRESS_GDT 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_RTCO_PHYSICAL_ADDRESS_GDT TYPE RTCO_PHYSICAL_ADDRESS_GDT.
The RTCO_PHYSICAL_ADDRESS_GDT 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 Data Element (Generated)), COUNTRY_NAME (), CONTROLLER (), LANGUAGE_CODE (Proxy Data Element (Generated)).. 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 RTCO_PHYSICAL_ADDRESS_GDT 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 Data Element (Generated) | RTCO_COUNTRY_CODE | CHAR | 3 | |||||
| COUNTRY_NAME | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LANGUAGE_CODE | Proxy Data Element (Generated) | RTCO_LANGUAGE_CODE | CHAR | 9 | |||||
| CONTENT | Proxy Data Element (Generated) | RTCO_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 | RTCO_AGENCY_IDENTIFICATION_COD | CHAR | 3 | |||||
| CONTENT | 0 | ||||||||
| REGION_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| STREET_POSTAL_CODE | Proxy Data Element (Generated) | RTCO_POSTAL_CODE | CHAR | 10 | |||||
| POBOX_POSTAL_CODE | Proxy Data Element (Generated) | RTCO_POSTAL_CODE | CHAR | 10 | |||||
| COMPANY_POSTAL_CODE | Proxy Data Element (Generated) | RTCO_POSTAL_CODE | CHAR | 10 | |||||
| CITY_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| ADDITIONAL_CITY_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| DISTRICT_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| POBOX_ID | Proxy Data Element (Generated) | RTCO_POBOX_ID | CHAR | 10 | |||||
| POBOX_INDICATOR | Indicator is the representation of a situation that has exac | RTCO_INDICATOR | CHAR | 5 | |||||
| POBOX_COUNTRY_CODE | Proxy Data Element (Generated) | RTCO_COUNTRY_CODE | CHAR | 3 | |||||
| POBOX_COUNTRY_NAME | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LANGUAGE_CODE | Proxy Data Element (Generated) | RTCO_LANGUAGE_CODE | CHAR | 9 | |||||
| CONTENT | Proxy Data Element (Generated) | RTCO_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 | RTCO_AGENCY_IDENTIFICATION_COD | CHAR | 3 | |||||
| CONTENT | 0 | ||||||||
| POBOX_REGION_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| POBOX_CITY_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| STREET_NAME | Proxy Data Element (Generated) | RTCO_STREET_NAME | CHAR | 60 | |||||
| STREET_PREFIX_NAME | 0 | ||||||||
| STREET_SUFFIX_NAME | 0 | ||||||||
| HOUSE_ID | Proxy Data Element (Generated) | RTCO_HOUSE_ID | CHAR | 10 | |||||
| ADDITIONAL_HOUSE_ID | Proxy Data Element (Generated) | RTCO_HOUSE_ID | CHAR | 10 | |||||
| BUILDING_ID | Proxy Data Element (Generated) | RTCO_BUILDING_ID | CHAR | 10 | |||||
| FLOOR_ID | Proxy Data Element (Generated) | RTCO_FLOOR_ID | CHAR | 10 | |||||
| ROOM_ID | Proxy Data Element (Generated) | RTCO_ROOM_ID | CHAR | 10 | |||||
| CARE_OF_NAME | Proxy Data Element (generated) | RTCO_LANGU_INDEP_MEDIUM_NAME | CHAR | 40 | |||||
| DESCRIPTION | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RTCO_PHYSICAL_ADDRESS_GDT using ABAP code?
As RTCO_PHYSICAL_ADDRESS_GDT 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 RTCO_PHYSICAL_ADDRESS_GDT as there is no data to select.How to access SAP table RTCO_PHYSICAL_ADDRESS_GDT
Within an ECC or HANA version of SAP you can also view further information about RTCO_PHYSICAL_ADDRESS_GDT 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