DYNP_RHPD_SEARCH SAP (Screen Processing: Function Group RHPD_SEARCH) Structure details
Description: Screen Processing: Function Group RHPD_SEARCH
Related tables to DYNP_RHPD_SEARCH
Access table DYNP_RHPD_SEARCH
Structure field list including key, data, relationships and ABAP select examples
DYNP_RHPD_SEARCH 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 "Screen Processing: Function Group RHPD_SEARCH" 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_DYNP_RHPD_SEARCH TYPE DYNP_RHPD_SEARCH.
The DYNP_RHPD_SEARCH table consists of various fields, each holding specific information or linking keys about Screen Processing: Function Group RHPD_SEARCH data available in SAP. These include REF_OBJID (Search Term), REF_STEXT (Object Name), BUTTON_OPTION (Icon in text fields (substitute display, alias)), STAG (Reporting key date).. 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 or numeric)
SAP DYNP_RHPD_SEARCH 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 |
| REF_OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
| REF_OBJID | Search Term | SEARK | CHAR | 12 | CHAR12 | ||||
| REF_STEXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| BUTTON_OPTION | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
| STAG | Reporting key date | KEYDAY | DATS | 8 | DATUM | ||||
| PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
| OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
| OBJID | Object ID | HROBJID | NUMC | 8 | Assigned to domain | HROBJID | PON | ||
| QUALSTXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| ESSENTIAL | Indicator: Essential or Optional Requirement | ESSENTIALX | CHAR | 1 | CHAR1_X | PEM | |||
| SIGN | Selection criteria: SIGN | RSSIGN | CHAR | 1 | RSSIGN | ||||
| OPTION | Selection criteria: OPTION | RSOPTION | CHAR | 2 | RSOPTION | ||||
| LOW | Proficiency of a Quality Scale | RATING | NUMC | 4 | CHARA | ||||
| HIGH | Proficiency of a Quality Scale | RATING | NUMC | 4 | CHARA | ||||
| LOW_TEXT | Proficiency | HRPDV_PROFCY_TEXT_LOW | CHAR | 40 | TEXT40 | ||||
| HIGH_TEXT | Maximum Proficiency | HRPDV_PROFCY_TEXT_HIGH | CHAR | 40 | TEXT40 | ||||
| SELECT_OTEXT | Object Type Text | OTEXT | CHAR | 25 | TEXT25 | ||||
| PERS_OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
| PERS_OBJID | Search Term | SEARK | CHAR | 12 | CHAR12 | ||||
| PERS_TAB_OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
| PERS_TAB_SOBID | ID of Related Object | SOBID | CHAR | 45 | CHAR45 | ||||
| PERS_TAB_OTEXT | Object Type Text | OTEXT | CHAR | 25 | TEXT25 | ||||
| PERS_TAB_STEXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| FRAME1 | Text Field of Length 60 | TEXT60 | CHAR | 60 | TEXT60 | ||||
| FRAME2 | Text Field of Length 60 | TEXT60 | CHAR | 60 | TEXT60 | ||||
| PLANNING_BEGDA | Planning Start Date | PLANNING_BEGDA | DATS | 8 | DATUM | ||||
| PLANNING_ENDDA | Planning End Date | PLANNING_ENDDA | DATS | 8 | DATUM | ||||
| PLANNING_DAY | Planning Days | PLANNING_DAY | DEC | 6(2) | DECV4_2 |
| Key field | Non-key field |
How do I retrieve data from SAP structure DYNP_RHPD_SEARCH using ABAP code?
As DYNP_RHPD_SEARCH 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 DYNP_RHPD_SEARCH as there is no data to select.How to access SAP table DYNP_RHPD_SEARCH
Within an ECC or HANA version of SAP you can also view further information about DYNP_RHPD_SEARCH 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