SAP GET_CONVERTED_TAB_REMOTE Function Module for Gets Remote Table, Converts It to Local Format (Physical + Log.)

Search SAP Function Modules

GET_CONVERTED_TAB_REMOTE is a standard get converted tab remote SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets Remote Table, Converts It to Local Format (Physical + Log.) 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 get converted tab remote FM, simply by entering the name GET_CONVERTED_TAB_REMOTE 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): Normal Function Module
Update:

Function GET_CONVERTED_TAB_REMOTE 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 'GET_CONVERTED_TAB_REMOTE'"Gets Remote Table, Converts It to Local Format (Physical + Log.)
  EXPORTING
*  CLIENT = 000 "Client where data is to be fetched
   HOST =  "Remote host where data originated
   TABLE_NAME =  "Name of the table to be fetched
*  GET_MODUS =  "Mode for possible conversion
*  GET_SYSTAB = ' ' "Yes/No (X/ )

 IMPORTING
   RFC_ERROR_TEXT =  "

TABLES
   TABLEBOX =  "Table contents

EXCEPTIONS
   CLIENT_NOT_FOUND = 1    LENGTH_ERROR = 10    HOST_NOT_REACHABLE = 11    PROTECTED = 2    READ_ERROR = 3    TABLE_NOT_FOUND = 4    TOO_SMALL = 5    TABLE_NOT_CONVERTIBLE = 6    WRONG_TYPE = 7    FIELDTAB_ERROR = 8    NO_RIGHTS = 9 

.

IMPORTING Parameters details for GET_CONVERTED_TAB_REMOTE

CLIENT - Client where data is to be fetched

Data type: T000-MANDT
Default: 000
Optional: Yes
Call by Reference: No ( called with pass by value option)

HOST - Remote host where data originated

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

TABLE_NAME - Name of the table to be fetched

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

GET_MODUS - Mode for possible conversion

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

GET_SYSTAB - Yes/No (X/ )

Data type: CCPROGPAR-CHK_SYSTAB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GET_CONVERTED_TAB_REMOTE

RFC_ERROR_TEXT -

Data type: CHAR80
Optional: No
Call by Reference: Yes

TABLES Parameters details for GET_CONVERTED_TAB_REMOTE

TABLEBOX - Table contents

Data type: TABLE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CLIENT_NOT_FOUND - Obsolete

Data type:
Optional: No
Call by Reference: Yes

LENGTH_ERROR -

Data type:
Optional: No
Call by Reference: Yes

HOST_NOT_REACHABLE -

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

PROTECTED - Table cannot be processed (INTTAB, systemtab)

Data type:
Optional: No
Call by Reference: Yes

READ_ERROR - Table cannot be read

Data type:
Optional: No
Call by Reference: Yes

TABLE_NOT_FOUND - Table not found

Data type:
Optional: No
Call by Reference: Yes

TOO_SMALL - Entries too long (larger than maximum box)

Data type:
Optional: No
Call by Reference: Yes

TABLE_NOT_CONVERTIBLE - Error During Translation

Data type:
Optional: No
Call by Reference: Yes

WRONG_TYPE -

Data type:
Optional: No
Call by Reference: Yes

FIELDTAB_ERROR - Error reading NAMETAB

Data type:
Optional: No
Call by Reference: Yes

NO_RIGHTS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GET_CONVERTED_TAB_REMOTE 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.

ABAP code using 7.40 inline data declarations to call FM GET_CONVERTED_TAB_REMOTE

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.

Search for further information about these or an SAP related objects