GTPARTIAL_UPDATE_ELEMENTS_DATA SAP (Proxy Structure (generated)) Structure details
Description: Proxy Structure (generated)
Related tables to GTPARTIAL_UPDATE_ELEMENTS_DATA
Access table GTPARTIAL_UPDATE_ELEMENTS_DATA
Structure field list including key, data, relationships and ABAP select examples
GTPARTIAL_UPDATE_ELEMENTS_DATA 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_GTPARTIAL_UPDATE_ELEMENTS_DATA TYPE GTPARTIAL_UPDATE_ELEMENTS_DATA.
The GTPARTIAL_UPDATE_ELEMENTS_DATA table consists of various fields, each holding specific information or linking keys about Proxy Structure (generated) data available in SAP. These include CHOICE (), SELECTION (Proxy Generation: Name of an Object in R/3), CONTROLLER (), TRAVELER ().. 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 GTPARTIAL_UPDATE_ELEMENTS_DATA 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 | ||||||||
| CHOICE | 0 | ||||||||
| SELECTION | Proxy Generation: Name of an Object in R/3 | PRX_R3NAME | CHAR | 30 | PRX_R3NAME | ||||
| CONTROLLER | 0 | ||||||||
| TRAVELER | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| BIRTH_DATE | XSD Date: yyyy-mm-dd [ext.] | XSDDATE_D | DATS | 8 | XSDDATE_D | ||||
| MARITAL_STATUS | Used for Character Strings, length 1 | GTSTRING_LENGTH1 | CHAR | 1 | |||||
| GENDER | 0 | ||||||||
| AGE_RANGE | Used for Character Strings, length 1 to 30 | GTSTRING_LENGTH1TO30 | CHAR | 30 | |||||
| PROFILE_NAME | Used for Character Strings, length 1 to 120 | GTSTRING_LENGTH1TO120 | CHAR | 120 | |||||
| DOMAIN_ID | Used for Character Strings, length 1 to 10 | GTSTRING_LENGTH1TO10 | CHAR | 10 | |||||
| PROFILE_STATUS | Status of the Profile AC-Active, DL- Mark for Delete, IN-Ina | GTSTATUS_TYPE | STRG | 0 | |||||
| LOGIN_ID | Used for Character Strings, length 1 to 120 | GTSTRING_LENGTH1TO120 | CHAR | 120 | |||||
| PASSWORD | Used for Character Strings, length 1 to 100 | GTSTRING_LENGTH1TO100 | CHAR | 100 | |||||
| DESCRIPTION | Used for Character Strings, length 1 to 255 | GTSTRING_LENGTH1TO255 | CHAR | 255 |
| Key field | Non-key field |
How do I retrieve data from SAP structure GTPARTIAL_UPDATE_ELEMENTS_DATA using ABAP code?
As GTPARTIAL_UPDATE_ELEMENTS_DATA 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 GTPARTIAL_UPDATE_ELEMENTS_DATA as there is no data to select.How to access SAP table GTPARTIAL_UPDATE_ELEMENTS_DATA
Within an ECC or HANA version of SAP you can also view further information about GTPARTIAL_UPDATE_ELEMENTS_DATA 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