SAP DD_TTYP_GET Function Module for DD: Read routine for table types









DD_TTYP_GET is a standard dd ttyp 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 table types 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 ttyp get FM, simply by entering the name DD_TTYP_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function DD_TTYP_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_TTYP_GET'"DD: Read routine for table types
EXPORTING
* GET_STATE = 'M ' "
* LANGU = SY-LANGU "Language in which Texts are Read
* PRID = 0 "
TTYP_NAME = "Name of Table Type to be Read
* WITHTEXT = ' ' "
* TRACELEVEL = 0 "Precision of log

IMPORTING
DD40V_WA_A = "
DD40V_WA_N = "
GOT_STATE = "

TABLES
* DD42V_TAB_A = "
* DD42V_TAB_N = "
* DD43V_TAB_A = "
* DD43V_TAB_N = "

EXCEPTIONS
ILLEGAL_VALUE = 1 OP_FAILURE = 2
.



IMPORTING Parameters details for DD_TTYP_GET

GET_STATE -

Data type: DCTTYPGET
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: SY-LANGU
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)

TTYP_NAME - Name of Table Type to be Read

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

WITHTEXT -

Data type: DDREFSTRUC-BOOL
Default: ' '
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)

EXPORTING Parameters details for DD_TTYP_GET

DD40V_WA_A -

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

DD40V_WA_N -

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

GOT_STATE -

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

TABLES Parameters details for DD_TTYP_GET

DD42V_TAB_A -

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

DD42V_TAB_N -

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

DD43V_TAB_A -

Data type: DD43V
Optional: Yes
Call by Reference: Yes

DD43V_TAB_N -

Data type: DD43V
Optional: Yes
Call by Reference: Yes

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_TTYP_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 DCTTYPGET, "   'M '
lv_dd40v_wa_a  TYPE DD40V, "   
lt_dd42v_tab_a  TYPE STANDARD TABLE OF DD42V, "   
lv_illegal_value  TYPE DD42V, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_dd40v_wa_n  TYPE DD40V, "   
lv_op_failure  TYPE DD40V, "   
lt_dd42v_tab_n  TYPE STANDARD TABLE OF DD42V, "   
lv_prid  TYPE SY-TABIX, "   0
lv_got_state  TYPE DCTTYPGET, "   
lt_dd43v_tab_a  TYPE STANDARD TABLE OF DD43V, "   
lv_ttyp_name  TYPE DD40L-TYPENAME, "   
lt_dd43v_tab_n  TYPE STANDARD TABLE OF DD43V, "   
lv_withtext  TYPE DDREFSTRUC-BOOL, "   ' '
lv_tracelevel  TYPE SY-TABIX. "   0

  CALL FUNCTION 'DD_TTYP_GET'  "DD: Read routine for table types
    EXPORTING
         GET_STATE = lv_get_state
         LANGU = lv_langu
         PRID = lv_prid
         TTYP_NAME = lv_ttyp_name
         WITHTEXT = lv_withtext
         TRACELEVEL = lv_tracelevel
    IMPORTING
         DD40V_WA_A = lv_dd40v_wa_a
         DD40V_WA_N = lv_dd40v_wa_n
         GOT_STATE = lv_got_state
    TABLES
         DD42V_TAB_A = lt_dd42v_tab_a
         DD42V_TAB_N = lt_dd42v_tab_n
         DD43V_TAB_A = lt_dd43v_tab_a
         DD43V_TAB_N = lt_dd43v_tab_n
    EXCEPTIONS
        ILLEGAL_VALUE = 1
        OP_FAILURE = 2
. " DD_TTYP_GET




ABAP code using 7.40 inline data declarations to call FM DD_TTYP_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.

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 TYPENAME FROM DD40L INTO @DATA(ld_ttyp_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



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!