SAP DD_TABL_PUT Function Module for
DD_TABL_PUT is a standard dd tabl put SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 tabl put FM, simply by entering the name DD_TABL_PUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDTB
Program Name: SAPLSDTB
Main Program: SAPLSDTB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_TABL_PUT 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_TABL_PUT'".
EXPORTING
* CTRL_TABL_PUT = 'XXXXXX' "
DD02V_WA = "Table header
DD09L_WA = "Technical settings
* PRID = 0 "
* PUT_STATE = 'N' "
* TABL_NAME = ' ' "Table Name
TABLES
* DD03P_TAB = "Field definition
* DD05M_TAB = "Foreign key fields
* DD08V_TAB = "
* DD35V_TAB = "
* DD36M_TAB = "
* DD12V_TAB = "
* DD17V_TAB = "Index Fields
EXCEPTIONS
DB_ACCESS_FAILURE = 1 OBJECT_INCONSISTENT = 2
IMPORTING Parameters details for DD_TABL_PUT
CTRL_TABL_PUT -
Data type: DCTABLPUTDefault: 'XXXXXX'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DD02V_WA - Table header
Data type: DD02VOptional: No
Call by Reference: No ( called with pass by value option)
DD09L_WA - Technical settings
Data type: DD09VOptional: No
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)
PUT_STATE -
Data type: DDREFSTRUC-STATEDefault: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABL_NAME - Table Name
Data type: DD02L-TABNAMEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DD_TABL_PUT
DD03P_TAB - Field definition
Data type: DD03POptional: Yes
Call by Reference: No ( called with pass by value option)
DD05M_TAB - Foreign key fields
Data type: DD05MOptional: Yes
Call by Reference: No ( called with pass by value option)
DD08V_TAB -
Data type: DD08VOptional: Yes
Call by Reference: No ( called with pass by value option)
DD35V_TAB -
Data type: DD35VOptional: Yes
Call by Reference: No ( called with pass by value option)
DD36M_TAB -
Data type: DD36MOptional: Yes
Call by Reference: No ( called with pass by value option)
DD12V_TAB -
Data type: DD12VOptional: Yes
Call by Reference: No ( called with pass by value option)
DD17V_TAB - Index Fields
Data type: DD17VOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_ACCESS_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_INCONSISTENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_TABL_PUT 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: | ||||
| lt_dd03p_tab | TYPE STANDARD TABLE OF DD03P, " | |||
| lv_ctrl_tabl_put | TYPE DCTABLPUT, " 'XXXXXX' | |||
| lv_db_access_failure | TYPE DCTABLPUT, " | |||
| lv_dd02v_wa | TYPE DD02V, " | |||
| lt_dd05m_tab | TYPE STANDARD TABLE OF DD05M, " | |||
| lv_object_inconsistent | TYPE DD05M, " | |||
| lv_dd09l_wa | TYPE DD09V, " | |||
| lt_dd08v_tab | TYPE STANDARD TABLE OF DD08V, " | |||
| lv_prid | TYPE SY-TABIX, " 0 | |||
| lt_dd35v_tab | TYPE STANDARD TABLE OF DD35V, " | |||
| lt_dd36m_tab | TYPE STANDARD TABLE OF DD36M, " | |||
| lv_put_state | TYPE DDREFSTRUC-STATE, " 'N' | |||
| lt_dd12v_tab | TYPE STANDARD TABLE OF DD12V, " | |||
| lv_tabl_name | TYPE DD02L-TABNAME, " ' ' | |||
| lt_dd17v_tab | TYPE STANDARD TABLE OF DD17V. " |
|   CALL FUNCTION 'DD_TABL_PUT' " |
| EXPORTING | ||
| CTRL_TABL_PUT | = lv_ctrl_tabl_put | |
| DD02V_WA | = lv_dd02v_wa | |
| DD09L_WA | = lv_dd09l_wa | |
| PRID | = lv_prid | |
| PUT_STATE | = lv_put_state | |
| TABL_NAME | = lv_tabl_name | |
| TABLES | ||
| DD03P_TAB | = lt_dd03p_tab | |
| DD05M_TAB | = lt_dd05m_tab | |
| DD08V_TAB | = lt_dd08v_tab | |
| DD35V_TAB | = lt_dd35v_tab | |
| DD36M_TAB | = lt_dd36m_tab | |
| DD12V_TAB | = lt_dd12v_tab | |
| DD17V_TAB | = lt_dd17v_tab | |
| EXCEPTIONS | ||
| DB_ACCESS_FAILURE = 1 | ||
| OBJECT_INCONSISTENT = 2 | ||
| . " DD_TABL_PUT | ||
ABAP code using 7.40 inline data declarations to call FM DD_TABL_PUT
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.| DATA(ld_ctrl_tabl_put) | = 'XXXXXX'. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_prid). | ||||
| "SELECT single STATE FROM DDREFSTRUC INTO @DATA(ld_put_state). | ||||
| DATA(ld_put_state) | = 'N'. | |||
| "SELECT single TABNAME FROM DD02L INTO @DATA(ld_tabl_name). | ||||
| DATA(ld_tabl_name) | = ' '. | |||
Search for further information about these or an SAP related objects