SAP RFC_TABLE_ACCESS Function Module for Internal Interface for Calling RFC Table Servers

Search SAP Function Modules

RFC_TABLE_ACCESS is a standard rfc table access SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal Interface for Calling RFC Table Servers 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 rfc table access FM, simply by entering the name RFC_TABLE_ACCESS into the relevant SAP transaction such as SE37 or SE38.

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

Function RFC_TABLE_ACCESS 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 'RFC_TABLE_ACCESS'"        Internal Interface for Calling RFC Table Servers
  EXPORTING
*  DESTINATION = 'NONE' "
*  FUNCTION = 'NONE' "
*  MESSAGE = 'GETLIST' "
*  OPTION = ' ' "
*  SERVERNAME = ' ' "

 IMPORTING
   ACTION =  "
   ERROR =  "

TABLES
   TAB_IN =  "
   TAB_OUT =  "
   TT_QUERY =  "

EXCEPTIONS
   COMMUNICATION_FAILURE = 1    SYSTEM_FAILURE = 2    UNSUPPORTED_METHOD = 3 

.

IMPORTING Parameters details for RFC_TABLE_ACCESS

DESTINATION -

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

FUNCTION -

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

MESSAGE -

Data type: SDIT_PARAM-MESSAGE
Default: 'GETLIST'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OPTION -

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

SERVERNAME -

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

EXPORTING Parameters details for RFC_TABLE_ACCESS

ACTION -

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

ERROR -

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

TABLES Parameters details for RFC_TABLE_ACCESS

TAB_IN -

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

TAB_OUT -

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

TT_QUERY -

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

EXCEPTIONS details

COMMUNICATION_FAILURE - Error when transferring data

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

SYSTEM_FAILURE - Error constructing communication

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

UNSUPPORTED_METHOD - Server exists but method unknown

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

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

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