SAP TABLE_ENTRIES_GET_VIA_RFC Function Module for

Search SAP Function Modules

TABLE_ENTRIES_GET_VIA_RFC is a standard table entries get via rfc 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 table entries get via rfc FM, simply by entering the name TABLE_ENTRIES_GET_VIA_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDCH
Program Name: SAPLBDCH
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TABLE_ENTRIES_GET_VIA_RFC 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 'TABLE_ENTRIES_GET_VIA_RFC'"
  EXPORTING
*  LANGU = SY-LANGU "
*  ONLY = ' ' "
*  TABNAME = ' ' "

 IMPORTING
   RC =  "

TABLES
   SEL_TAB =  "
   NAMETAB =  "
   TABENTRY =  "

EXCEPTIONS
   INTERNAL_ERROR = 1    TABLE_HAS_NO_FIELDS = 2    TABLE_NOT_ACTIV = 3    NOT_AUTHORIZED = 4 

.

IMPORTING Parameters details for TABLE_ENTRIES_GET_VIA_RFC

LANGU -

Data type: DNTAB-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

ONLY -

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

TABNAME -

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

EXPORTING Parameters details for TABLE_ENTRIES_GET_VIA_RFC

RC -

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

TABLES Parameters details for TABLE_ENTRIES_GET_VIA_RFC

SEL_TAB -

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

NAMETAB -

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

TABENTRY -

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

EXCEPTIONS details

INTERNAL_ERROR -

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

TABLE_HAS_NO_FIELDS -

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

TABLE_NOT_ACTIV -

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

NOT_AUTHORIZED -

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

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

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