DD_SHHD_GET SAP Function module - DD: Read routine for sub-object search help header (SHHD)

DD_SHHD_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DD_SHHD_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SDSH
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM DD_SHHD_GET - DD SHHD GET

CALL FUNCTION 'DD_SHHD_GET' "DD: Read routine for sub-object search help header (SHHD)
  EXPORTING
*   get_state = 'M'             " ddrefstruc-state
*   langu = SY-LANGU            " sy-langu      Language in which Texts are Read
*   prid = 0                    " sy-tabix
    shlp_name =                 " dd30l-shlpname  Name of search help to be read
*   withtext = ' '              " ddrefstruc-bool
*   tracelevel = 0              " sy-tabix      Precision of log
  IMPORTING
    dd30v_wa_a =                " dd30v
    dd30v_wa_n =                " dd30v
    got_state =                 " ddrefstruc-state
  EXCEPTIONS
    ILLEGAL_VALUE = 1           "               Value not allowed for parameter
    OP_FAILURE = 2              "               Internal Error
    .  "  DD_SHHD_GET

ABAP code example for Function Module DD_SHHD_GET

The ABAP code below is a full code listing to execute function module DD_SHHD_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_dd30v_wa_a  
 
 TYPE DD30V
,
ld_dd30v_wa_n  
 
 TYPE DD30V
,
ld_got_state  
 
 TYPE DDREFSTRUC-STATE
.



DATA(ld_get_state) = some text here

DATA(ld_langu) = 'Check type of data required'.

DATA(ld_prid) = '123 '.
 

SELECT single SHLPNAME 
  FROM DD30L 
  INTO @DATA(ld_shlp_name).



DATA(ld_withtext) = some text here

DATA(ld_tracelevel) = '123 '.
.

CALL FUNCTION 'DD_SHHD_GET'
  EXPORTING
*   get_state =                  ld_get_state
*   langu =                      ld_langu
*   prid =                       ld_prid
    shlp_name =                  ld_shlp_name
*   withtext =                   ld_withtext
*   tracelevel =                 ld_tracelevel
  IMPORTING
    dd30v_wa_a =                 ld_dd30v_wa_a
    dd30v_wa_n =                 ld_dd30v_wa_n
    got_state =                  ld_got_state
  EXCEPTIONS
    ILLEGAL_VALUE =              1
    OP_FAILURE =                 2
    .  "  DD_SHHD_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_dd30v_wa_a
 
 TYPE DD30V ,
ld_get_state
 
 TYPE DDREFSTRUC-STATE ,
ld_dd30v_wa_n
 
 TYPE DD30V ,
ld_langu
 
 TYPE SY-LANGU ,
ld_got_state
 
 TYPE DDREFSTRUC-STATE ,
ld_prid
 
 TYPE SY-TABIX ,
ld_shlp_name
 
 TYPE DD30L-SHLPNAME ,
ld_withtext
 
 TYPE DDREFSTRUC-BOOL ,
ld_tracelevel
 
 TYPE SY-TABIX .



ld_get_state = some text here
ld_langu = 'Check type of data required'.
ld_prid = '123 '.

SELECT single SHLPNAME 
  FROM DD30L 
  INTO ld_shlp_name.


ld_withtext = some text here
ld_tracelevel = '123 '.