SAP DD_SHHD_GET Function Module for DD: Read routine for sub-object search help header (SHHD)
DD_SHHD_GET is a standard dd shhd get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Read routine for sub-object search help header (SHHD) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for dd shhd get FM, simply by entering the name DD_SHHD_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDSH
Program Name: SAPLSDSH
Main Program: SAPLSDSH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_SHHD_GET pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'DD_SHHD_GET'"DD: Read routine for sub-object search help header (SHHD).
EXPORTING
* GET_STATE = 'M' "
* LANGU = SY-LANGU "Language in which Texts are Read
* PRID = 0 "
SHLP_NAME = "Name of search help to be read
* WITHTEXT = ' ' "
* TRACELEVEL = 0 "Precision of log
IMPORTING
DD30V_WA_A = "
DD30V_WA_N = "
GOT_STATE = "
EXCEPTIONS
ILLEGAL_VALUE = 1 OP_FAILURE = 2
IMPORTING Parameters details for DD_SHHD_GET
GET_STATE -
Data type: DDREFSTRUC-STATEDefault: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGU - Language in which Texts are Read
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
PRID -
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
SHLP_NAME - Name of search help to be read
Data type: DD30L-SHLPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
WITHTEXT -
Data type: DDREFSTRUC-BOOLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRACELEVEL - Precision of log
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_SHHD_GET
DD30V_WA_A -
Data type: DD30VOptional: No
Call by Reference: No ( called with pass by value option)
DD30V_WA_N -
Data type: DD30VOptional: No
Call by Reference: No ( called with pass by value option)
GOT_STATE -
Data type: DDREFSTRUC-STATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_VALUE - Value not allowed for parameter
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OP_FAILURE - Internal Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_SHHD_GET Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_get_state | TYPE DDREFSTRUC-STATE, " 'M' | |||
| lv_dd30v_wa_a | TYPE DD30V, " | |||
| lv_illegal_value | TYPE DD30V, " | |||
| lv_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_dd30v_wa_n | TYPE DD30V, " | |||
| lv_op_failure | TYPE DD30V, " | |||
| lv_prid | TYPE SY-TABIX, " 0 | |||
| lv_got_state | TYPE DDREFSTRUC-STATE, " | |||
| lv_shlp_name | TYPE DD30L-SHLPNAME, " | |||
| lv_withtext | TYPE DDREFSTRUC-BOOL, " ' ' | |||
| lv_tracelevel | TYPE SY-TABIX. " 0 |
|   CALL FUNCTION 'DD_SHHD_GET' "DD: Read routine for sub-object search help header (SHHD) |
| EXPORTING | ||
| GET_STATE | = lv_get_state | |
| LANGU | = lv_langu | |
| PRID | = lv_prid | |
| SHLP_NAME | = lv_shlp_name | |
| WITHTEXT | = lv_withtext | |
| TRACELEVEL | = lv_tracelevel | |
| IMPORTING | ||
| DD30V_WA_A | = lv_dd30v_wa_a | |
| DD30V_WA_N | = lv_dd30v_wa_n | |
| GOT_STATE | = lv_got_state | |
| EXCEPTIONS | ||
| ILLEGAL_VALUE = 1 | ||
| OP_FAILURE = 2 | ||
| . " DD_SHHD_GET | ||
ABAP code using 7.40 inline data declarations to call FM DD_SHHD_GET
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single STATE FROM DDREFSTRUC INTO @DATA(ld_get_state). | ||||
| DATA(ld_get_state) | = 'M'. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_langu). | ||||
| DATA(ld_langu) | = SY-LANGU. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_prid). | ||||
| "SELECT single STATE FROM DDREFSTRUC INTO @DATA(ld_got_state). | ||||
| "SELECT single SHLPNAME FROM DD30L INTO @DATA(ld_shlp_name). | ||||
| "SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_withtext). | ||||
| DATA(ld_withtext) | = ' '. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_tracelevel). | ||||
Search for further information about these or an SAP related objects