TPR1_DYNP SAP (Partner-Object Relationship: Assignment Category Texts) Structure details
Description: Partner-Object Relationship: Assignment Category Texts
Structure field list including key, data, relationships and ABAP select examples
TPR1_DYNP 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 "Partner-Object Relationship: Assignment Category Texts" 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_TPR1_DYNP TYPE TPR1_DYNP.
The TPR1_DYNP table consists of various fields, each holding specific information or linking keys about Partner-Object Relationship: Assignment Category Texts data available in SAP. These include CLIENT (Client), SPRAS (Language Key), ASSI_TYP (Assignment Category), BEZ30 (Description).. 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 (character-type)
SAP TPR1_DYNP 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 |
| CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| ASSI_TYP | Assignment Category | BP_ASSI_TYP | CHAR | 6 | Assigned to domain | BP_ASSI_TYP | |||
| BEZ30 | Description | BU_BEZ30 | CHAR | 30 | TEXT30 | ||||
| MARK | Checkbox | XFELD | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure TPR1_DYNP using ABAP code?
As TPR1_DYNP 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 TPR1_DYNP as there is no data to select.How to access SAP table TPR1_DYNP
Within an ECC or HANA version of SAP you can also view further information about TPR1_DYNP 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