SAP SRTT_GET_REMOTE_TABLE_DEF Function Module for
SRTT_GET_REMOTE_TABLE_DEF is a standard srtt get remote table def 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 srtt get remote table def FM, simply by entering the name SRTT_GET_REMOTE_TABLE_DEF into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRTT
Program Name: SAPLSRTT
Main Program: SAPLSRTT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SRTT_GET_REMOTE_TABLE_DEF 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 'SRTT_GET_REMOTE_TABLE_DEF'".
EXPORTING
IV_TABNAME = "
IMPORTING
EV_GOTSTATE = "
EV_DD02V = "
EV_DD09L = "
ET_TADIR = "
TABLES
DD03P_TAB = "
DD05M_TAB = "
DD08V_TAB = "
DD12V_TAB = "
DD17V_TAB = "
DD35V_TAB = "
DD36M_TAB = "
EXCEPTIONS
INVALID = 1 NO_AUTHORITY = 2 NOT_FOUND = 3
IMPORTING Parameters details for SRTT_GET_REMOTE_TABLE_DEF
IV_TABNAME -
Data type: DD02L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SRTT_GET_REMOTE_TABLE_DEF
EV_GOTSTATE -
Data type: DCOBJIF-GOTSTATEOptional: No
Call by Reference: No ( called with pass by value option)
EV_DD02V -
Data type: DD02VOptional: No
Call by Reference: No ( called with pass by value option)
EV_DD09L -
Data type: DD09LOptional: No
Call by Reference: No ( called with pass by value option)
ET_TADIR -
Data type: TADIROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SRTT_GET_REMOTE_TABLE_DEF
DD03P_TAB -
Data type: DD03POptional: No
Call by Reference: No ( called with pass by value option)
DD05M_TAB -
Data type: DD05MOptional: No
Call by Reference: No ( called with pass by value option)
DD08V_TAB -
Data type: DD08VOptional: No
Call by Reference: No ( called with pass by value option)
DD12V_TAB -
Data type: DD12VOptional: No
Call by Reference: No ( called with pass by value option)
DD17V_TAB -
Data type: DD17VOptional: No
Call by Reference: No ( called with pass by value option)
DD35V_TAB -
Data type: DD35VOptional: No
Call by Reference: No ( called with pass by value option)
DD36M_TAB -
Data type: DD36MOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SRTT_GET_REMOTE_TABLE_DEF 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_invalid | TYPE STRING, " | |||
| lt_dd03p_tab | TYPE STANDARD TABLE OF DD03P, " | |||
| lv_iv_tabname | TYPE DD02L-TABNAME, " | |||
| lv_ev_gotstate | TYPE DCOBJIF-GOTSTATE, " | |||
| lv_ev_dd02v | TYPE DD02V, " | |||
| lt_dd05m_tab | TYPE STANDARD TABLE OF DD05M, " | |||
| lv_no_authority | TYPE DD05M, " | |||
| lv_ev_dd09l | TYPE DD09L, " | |||
| lt_dd08v_tab | TYPE STANDARD TABLE OF DD08V, " | |||
| lv_not_found | TYPE DD08V, " | |||
| lv_et_tadir | TYPE TADIR, " | |||
| lt_dd12v_tab | TYPE STANDARD TABLE OF DD12V, " | |||
| lt_dd17v_tab | TYPE STANDARD TABLE OF DD17V, " | |||
| lt_dd35v_tab | TYPE STANDARD TABLE OF DD35V, " | |||
| lt_dd36m_tab | TYPE STANDARD TABLE OF DD36M. " |
|   CALL FUNCTION 'SRTT_GET_REMOTE_TABLE_DEF' " |
| EXPORTING | ||
| IV_TABNAME | = lv_iv_tabname | |
| IMPORTING | ||
| EV_GOTSTATE | = lv_ev_gotstate | |
| EV_DD02V | = lv_ev_dd02v | |
| EV_DD09L | = lv_ev_dd09l | |
| ET_TADIR | = lv_et_tadir | |
| TABLES | ||
| DD03P_TAB | = lt_dd03p_tab | |
| DD05M_TAB | = lt_dd05m_tab | |
| DD08V_TAB | = lt_dd08v_tab | |
| DD12V_TAB | = lt_dd12v_tab | |
| DD17V_TAB | = lt_dd17v_tab | |
| DD35V_TAB | = lt_dd35v_tab | |
| DD36M_TAB | = lt_dd36m_tab | |
| EXCEPTIONS | ||
| INVALID = 1 | ||
| NO_AUTHORITY = 2 | ||
| NOT_FOUND = 3 | ||
| . " SRTT_GET_REMOTE_TABLE_DEF | ||
ABAP code using 7.40 inline data declarations to call FM SRTT_GET_REMOTE_TABLE_DEF
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 TABNAME FROM DD02L INTO @DATA(ld_iv_tabname). | ||||
| "SELECT single GOTSTATE FROM DCOBJIF INTO @DATA(ld_ev_gotstate). | ||||
Search for further information about these or an SAP related objects