SAP DD_TBHD_SET_GET Function Module for DD: Interface to set-oriented reading: Table header









DD_TBHD_SET_GET is a standard dd tbhd set 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: Interface to set-oriented reading: Table header 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 tbhd set get FM, simply by entering the name DD_TBHD_SET_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDSG
Program Name: SAPLSDSG
Main Program: SAPLSDSG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DD_TBHD_SET_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_TBHD_SET_GET'"DD: Interface to set-oriented reading: Table header
EXPORTING
* GET_STATE = 'M' "
* LANGU = 'D' "Language in which Texts are Read
* PRID = 0 "
* WITHTEXT = 'X' "
* POINTER = ' ' "
* OFF = 0 "Do not use
* LEN = 0 "Do not use
* TRACELEVEL = 0 "Precision of log

TABLES
TABLNAMES = "
* DD02V_TAB_A = "
* DD02V_TAB_N = "
* GOT_STATES = "

EXCEPTIONS
ILLEGAL_VALUE = 1 OP_FAILURE = 2
.



IMPORTING Parameters details for DD_TBHD_SET_GET

GET_STATE -

Data type: DDREFSTRUC-STATE
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGU - Language in which Texts are Read

Data type: SY-LANGU
Default: 'D'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PRID -

Data type: SY-TABIX
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITHTEXT -

Data type: DDREFSTRUC-BOOL
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

POINTER -

Data type: FNAM_____4
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

OFF - Do not use

Data type: SY-FDPOS
Optional: Yes
Call by Reference: No ( called with pass by value option)

LEN - Do not use

Data type: SY-FDPOS
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRACELEVEL - Precision of log

Data type: SY-TABIX
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DD_TBHD_SET_GET

TABLNAMES -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DD02V_TAB_A -

Data type: DD02V
Optional: Yes
Call by Reference: No ( called with pass by value option)

DD02V_TAB_N -

Data type: DD02V
Optional: Yes
Call by Reference: No ( called with pass by value option)

GOT_STATES -

Data type: DDSTATE
Optional: Yes
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_TBHD_SET_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'
lt_tablnames  TYPE STANDARD TABLE OF DDREFSTRUC, "   
lv_illegal_value  TYPE DDREFSTRUC, "   
lv_langu  TYPE SY-LANGU, "   'D'
lv_op_failure  TYPE SY, "   
lt_dd02v_tab_a  TYPE STANDARD TABLE OF DD02V, "   
lv_prid  TYPE SY-TABIX, "   0
lt_dd02v_tab_n  TYPE STANDARD TABLE OF DD02V, "   
lv_withtext  TYPE DDREFSTRUC-BOOL, "   'X'
lt_got_states  TYPE STANDARD TABLE OF DDSTATE, "   
lv_pointer  TYPE FNAM_____4, "   ' '
lv_off  TYPE SY-FDPOS, "   0
lv_len  TYPE SY-FDPOS, "   0
lv_tracelevel  TYPE SY-TABIX. "   0

  CALL FUNCTION 'DD_TBHD_SET_GET'  "DD: Interface to set-oriented reading: Table header
    EXPORTING
         GET_STATE = lv_get_state
         LANGU = lv_langu
         PRID = lv_prid
         WITHTEXT = lv_withtext
         POINTER = lv_pointer
         OFF = lv_off
         LEN = lv_len
         TRACELEVEL = lv_tracelevel
    TABLES
         TABLNAMES = lt_tablnames
         DD02V_TAB_A = lt_dd02v_tab_a
         DD02V_TAB_N = lt_dd02v_tab_n
         GOT_STATES = lt_got_states
    EXCEPTIONS
        ILLEGAL_VALUE = 1
        OP_FAILURE = 2
. " DD_TBHD_SET_GET




ABAP code using 7.40 inline data declarations to call FM DD_TBHD_SET_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) = 'D'.
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_prid).
 
 
"SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_withtext).
DATA(ld_withtext) = 'X'.
 
 
DATA(ld_pointer) = ' '.
 
"SELECT single FDPOS FROM SY INTO @DATA(ld_off).
 
"SELECT single FDPOS FROM SY INTO @DATA(ld_len).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_tracelevel).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!