SAP Function Modules
G_TABLE_SELECT_WITH_CURSOR_RFC SAP Function module
G_TABLE_SELECT_WITH_CURSOR_RFC is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name G_TABLE_SELECT_WITH_CURSOR_RFC into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
GUSLRFC
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM G_TABLE_SELECT_WITH_CURSOR_RFC - G TABLE SELECT WITH CURSOR RFC
CALL FUNCTION 'G_TABLE_SELECT_WITH_CURSOR_RFC' "
EXPORTING
i_tabname = " tabname
i_bukrs_glob = " bukrs_glob
* i_selection = " gusl_t_selection_rfc
* i_fieldlist = " gusl_t_fields_rfc
* i_sortlist = " gusl_t_fields_rfc
* i_aggregation = " gusl_bool
* i_period_aggregation = " gusl_peraggr
* i_cumulated = " gusl_bool
* i_appending_table = " gusl_bool
* i_zero_records = " gusl_bool
* i_sorted = " gusl_bool
* i_client_specified = " gusl_bool
* i_db_commit = " gusl_bool
* i_field1 = " comp_field
* i_field2 = " comp_field
* i_dbcon_name = " dbcon_name
CHANGING
c_t_glu1 = " gusl_t_data_rfc
EXCEPTIONS
INTERNAL_ERROR = 1 "
LOGON_ERROR = 2 "
. " G_TABLE_SELECT_WITH_CURSOR_RFC
ABAP code example for Function Module G_TABLE_SELECT_WITH_CURSOR_RFC
The ABAP code below is a full code listing to execute function module G_TABLE_SELECT_WITH_CURSOR_RFC including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
DATA(ld_c_t_glu1) = 'Check type of data required'.
DATA(ld_i_tabname) = 'Check type of data required'.
DATA(ld_i_bukrs_glob) = 'Check type of data required'.
DATA(ld_i_selection) = 'Check type of data required'.
DATA(ld_i_fieldlist) = 'Check type of data required'.
DATA(ld_i_sortlist) = 'Check type of data required'.
DATA(ld_i_aggregation) = 'Check type of data required'.
DATA(ld_i_period_aggregation) = 'Check type of data required'.
DATA(ld_i_cumulated) = 'Check type of data required'.
DATA(ld_i_appending_table) = 'Check type of data required'.
DATA(ld_i_zero_records) = 'Check type of data required'.
DATA(ld_i_sorted) = 'Check type of data required'.
DATA(ld_i_client_specified) = 'Check type of data required'.
DATA(ld_i_db_commit) = 'Check type of data required'.
DATA(ld_i_field1) = 'Check type of data required'.
DATA(ld_i_field2) = 'Check type of data required'.
DATA(ld_i_dbcon_name) = 'Check type of data required'. . CALL FUNCTION 'G_TABLE_SELECT_WITH_CURSOR_RFC' EXPORTING i_tabname = ld_i_tabname i_bukrs_glob = ld_i_bukrs_glob * i_selection = ld_i_selection * i_fieldlist = ld_i_fieldlist * i_sortlist = ld_i_sortlist * i_aggregation = ld_i_aggregation * i_period_aggregation = ld_i_period_aggregation * i_cumulated = ld_i_cumulated * i_appending_table = ld_i_appending_table * i_zero_records = ld_i_zero_records * i_sorted = ld_i_sorted * i_client_specified = ld_i_client_specified * i_db_commit = ld_i_db_commit * i_field1 = ld_i_field1 * i_field2 = ld_i_field2 * i_dbcon_name = ld_i_dbcon_name CHANGING c_t_glu1 = ld_c_t_glu1 EXCEPTIONS INTERNAL_ERROR = 1 LOGON_ERROR = 2 . " G_TABLE_SELECT_WITH_CURSOR_RFC
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_c_t_glu1 | TYPE GUSL_T_DATA_RFC , |
| ld_i_tabname | TYPE TABNAME , |
| ld_i_bukrs_glob | TYPE BUKRS_GLOB , |
| ld_i_selection | TYPE GUSL_T_SELECTION_RFC , |
| ld_i_fieldlist | TYPE GUSL_T_FIELDS_RFC , |
| ld_i_sortlist | TYPE GUSL_T_FIELDS_RFC , |
| ld_i_aggregation | TYPE GUSL_BOOL , |
| ld_i_period_aggregation | TYPE GUSL_PERAGGR , |
| ld_i_cumulated | TYPE GUSL_BOOL , |
| ld_i_appending_table | TYPE GUSL_BOOL , |
| ld_i_zero_records | TYPE GUSL_BOOL , |
| ld_i_sorted | TYPE GUSL_BOOL , |
| ld_i_client_specified | TYPE GUSL_BOOL , |
| ld_i_db_commit | TYPE GUSL_BOOL , |
| ld_i_field1 | TYPE COMP_FIELD , |
| ld_i_field2 | TYPE COMP_FIELD , |
| ld_i_dbcon_name | TYPE DBCON_NAME . |
ld_c_t_glu1 = 'Check type of data required'.
ld_i_tabname = 'Check type of data required'.
ld_i_bukrs_glob = 'Check type of data required'.
ld_i_selection = 'Check type of data required'.
ld_i_fieldlist = 'Check type of data required'.
ld_i_sortlist = 'Check type of data required'.
ld_i_aggregation = 'Check type of data required'.
ld_i_period_aggregation = 'Check type of data required'.
ld_i_cumulated = 'Check type of data required'.
ld_i_appending_table = 'Check type of data required'.
ld_i_zero_records = 'Check type of data required'.
ld_i_sorted = 'Check type of data required'.
ld_i_client_specified = 'Check type of data required'.
ld_i_db_commit = 'Check type of data required'.
ld_i_field1 = 'Check type of data required'.
ld_i_field2 = 'Check type of data required'.
ld_i_dbcon_name = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name G_TABLE_SELECT_WITH_CURSOR_RFC or its description.