SAP BBP_RFC_READ_TABLE Function Module for NOTRANSL: External access to R/3 tables via RFC
BBP_RFC_READ_TABLE is a standard bbp rfc read table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: External access to R/3 tables via RFC 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 bbp rfc read table FM, simply by entering the name BBP_RFC_READ_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBPB
Program Name: SAPLBBPB
Main Program: SAPLBBPB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_RFC_READ_TABLE 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 'BBP_RFC_READ_TABLE'"NOTRANSL: External access to R/3 tables via RFC.
EXPORTING
QUERY_TABLE = "Table Name
* DELIMITER = ' ' "Text field length 1
* NO_DATA = ' ' "Text field length 1
* ROWSKIPS = 0 "SAPoffice: Type I
* ROWCOUNT = 0 "SAPoffice: Type I
TABLES
OPTIONS = "RFC Table Read: Select Options / WHERE Clause
FIELDS = "RFC Table Read: Description of Fields to Retrieve
DATA = "Table with a 512 byte field
EXCEPTIONS
TABLE_NOT_AVAILABLE = 1 TABLE_WITHOUT_DATA = 2 FIELD_NOT_VALID = 3 NOT_AUTHORIZED = 4 DATA_BUFFER_EXCEEDED = 5
IMPORTING Parameters details for BBP_RFC_READ_TABLE
QUERY_TABLE - Table Name
Data type: DD02L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
DELIMITER - Text field length 1
Data type: SONV-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_DATA - Text field length 1
Data type: SONV-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ROWSKIPS - SAPoffice: Type I
Data type: SOID-ACCNTOptional: Yes
Call by Reference: No ( called with pass by value option)
ROWCOUNT - SAPoffice: Type I
Data type: SOID-ACCNTOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_RFC_READ_TABLE
OPTIONS - RFC Table Read: Select Options / WHERE Clause
Data type: RFC_DB_OPTOptional: No
Call by Reference: Yes
FIELDS - RFC Table Read: Description of Fields to Retrieve
Data type: RFC_DB_FLDOptional: No
Call by Reference: Yes
DATA - Table with a 512 byte field
Data type: TAB512Optional: No
Call by Reference: Yes
EXCEPTIONS details
TABLE_NOT_AVAILABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
TABLE_WITHOUT_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
FIELD_NOT_VALID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
DATA_BUFFER_EXCEEDED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_RFC_READ_TABLE 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: | ||||
| lt_options | TYPE STANDARD TABLE OF RFC_DB_OPT, " | |||
| lv_query_table | TYPE DD02L-TABNAME, " | |||
| lv_table_not_available | TYPE DD02L, " | |||
| lt_fields | TYPE STANDARD TABLE OF RFC_DB_FLD, " | |||
| lv_delimiter | TYPE SONV-FLAG, " SPACE | |||
| lv_table_without_data | TYPE SONV, " | |||
| lt_data | TYPE STANDARD TABLE OF TAB512, " | |||
| lv_no_data | TYPE SONV-FLAG, " SPACE | |||
| lv_field_not_valid | TYPE SONV, " | |||
| lv_rowskips | TYPE SOID-ACCNT, " 0 | |||
| lv_not_authorized | TYPE SOID, " | |||
| lv_rowcount | TYPE SOID-ACCNT, " 0 | |||
| lv_data_buffer_exceeded | TYPE SOID. " |
|   CALL FUNCTION 'BBP_RFC_READ_TABLE' "NOTRANSL: External access to R/3 tables via RFC |
| EXPORTING | ||
| QUERY_TABLE | = lv_query_table | |
| DELIMITER | = lv_delimiter | |
| NO_DATA | = lv_no_data | |
| ROWSKIPS | = lv_rowskips | |
| ROWCOUNT | = lv_rowcount | |
| TABLES | ||
| OPTIONS | = lt_options | |
| FIELDS | = lt_fields | |
| DATA | = lt_data | |
| EXCEPTIONS | ||
| TABLE_NOT_AVAILABLE = 1 | ||
| TABLE_WITHOUT_DATA = 2 | ||
| FIELD_NOT_VALID = 3 | ||
| NOT_AUTHORIZED = 4 | ||
| DATA_BUFFER_EXCEEDED = 5 | ||
| . " BBP_RFC_READ_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_RFC_READ_TABLE
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_query_table). | ||||
| "SELECT single FLAG FROM SONV INTO @DATA(ld_delimiter). | ||||
| DATA(ld_delimiter) | = ' '. | |||
| "SELECT single FLAG FROM SONV INTO @DATA(ld_no_data). | ||||
| DATA(ld_no_data) | = ' '. | |||
| "SELECT single ACCNT FROM SOID INTO @DATA(ld_rowskips). | ||||
| "SELECT single ACCNT FROM SOID INTO @DATA(ld_rowcount). | ||||
Search for further information about these or an SAP related objects