SAP Function Modules
RKE_READ_OBJECTS SAP Function module
RKE_READ_OBJECTS 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 RKE_READ_OBJECTS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
KED1
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM RKE_READ_OBJECTS - RKE READ OBJECTS
CALL FUNCTION 'RKE_READ_OBJECTS' "
EXPORTING
erkrs = " tkeb-erkrs Financial statement area
* pa_type = '1' " ceddb-pa_type
* method = '1' " ceddb-method Method, allowed values: 1, 2, 3, 4
s_program_name = " ceddb-program Program which contains processing routines
s_form_name = " ceddb-dataform Routine for processing the data
* s_form_name_timestamp = SPACE " ceddb-tstmpform Routine for processing the point in time
* s_form_name_syncpoint = SPACE " ceddb-tstmpform
* read_source = '0' " ceddb-source Tables which are read (see domain)
* read_defined = '0' " ceddb-defined Read method (see domain values)
* read_timestamp = 0 " ceddb-timestmp Point in time as of which data is read
* caller_appl = '00' " tketrprot-caller_appl
* caller_detail = ' ' " tketrprot-caller_detail
* ignore_valutyp = ' ' " flag
IMPORTING
data_read_defined = " ceddb-flag Flag: data were read in a defined manner
TABLES
selection_table = " cedst Selected characteristics
EXCEPTIONS
FOREIGN_LOCK = 1 " No blocking possible for READ_DEFINED<>0
I_ERKRS_NOTFOUND = 2 " Financial statement area not defin
NO_RECORD_FOUND = 3 " No data record found which corresp
. " RKE_READ_OBJECTS
ABAP code example for Function Module RKE_READ_OBJECTS
The ABAP code below is a full code listing to execute function module RKE_READ_OBJECTS 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).
| ld_data_read_defined | TYPE CEDDB-FLAG , |
| it_selection_table | TYPE STANDARD TABLE OF CEDST,"TABLES PARAM |
| wa_selection_table | LIKE LINE OF it_selection_table . |
SELECT single ERKRS
FROM TKEB
INTO @DATA(ld_erkrs).
DATA(ld_pa_type) = some text here
DATA(ld_method) = some text here
DATA(ld_s_program_name) = some text here
DATA(ld_s_form_name) = some text here
DATA(ld_s_form_name_timestamp) = some text here
DATA(ld_s_form_name_syncpoint) = some text here
DATA(ld_read_source) = some text here
DATA(ld_read_defined) = some text here
DATA(ld_read_timestamp) = Check type of data required
SELECT single CALLER_APPL
FROM TKETRPROT
INTO @DATA(ld_caller_appl).
SELECT single CALLER_DETAIL
FROM TKETRPROT
INTO @DATA(ld_caller_detail).
DATA(ld_ignore_valutyp) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_selection_table to it_selection_table. . CALL FUNCTION 'RKE_READ_OBJECTS' EXPORTING erkrs = ld_erkrs * pa_type = ld_pa_type * method = ld_method s_program_name = ld_s_program_name s_form_name = ld_s_form_name * s_form_name_timestamp = ld_s_form_name_timestamp * s_form_name_syncpoint = ld_s_form_name_syncpoint * read_source = ld_read_source * read_defined = ld_read_defined * read_timestamp = ld_read_timestamp * caller_appl = ld_caller_appl * caller_detail = ld_caller_detail * ignore_valutyp = ld_ignore_valutyp IMPORTING data_read_defined = ld_data_read_defined TABLES selection_table = it_selection_table EXCEPTIONS FOREIGN_LOCK = 1 I_ERKRS_NOTFOUND = 2 NO_RECORD_FOUND = 3 . " RKE_READ_OBJECTS
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 ELSEIF SY-SUBRC EQ 3. "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_data_read_defined | TYPE CEDDB-FLAG , |
| ld_erkrs | TYPE TKEB-ERKRS , |
| it_selection_table | TYPE STANDARD TABLE OF CEDST , |
| wa_selection_table | LIKE LINE OF it_selection_table, |
| ld_pa_type | TYPE CEDDB-PA_TYPE , |
| ld_method | TYPE CEDDB-METHOD , |
| ld_s_program_name | TYPE CEDDB-PROGRAM , |
| ld_s_form_name | TYPE CEDDB-DATAFORM , |
| ld_s_form_name_timestamp | TYPE CEDDB-TSTMPFORM , |
| ld_s_form_name_syncpoint | TYPE CEDDB-TSTMPFORM , |
| ld_read_source | TYPE CEDDB-SOURCE , |
| ld_read_defined | TYPE CEDDB-DEFINED , |
| ld_read_timestamp | TYPE CEDDB-TIMESTMP , |
| ld_caller_appl | TYPE TKETRPROT-CALLER_APPL , |
| ld_caller_detail | TYPE TKETRPROT-CALLER_DETAIL , |
| ld_ignore_valutyp | TYPE FLAG . |
SELECT single ERKRS
FROM TKEB
INTO ld_erkrs.
"populate fields of struture and append to itab
append wa_selection_table to it_selection_table.
ld_pa_type = some text here
ld_method = some text here
ld_s_program_name = some text here
ld_s_form_name = some text here
ld_s_form_name_timestamp = some text here
ld_s_form_name_syncpoint = some text here
ld_read_source = some text here
ld_read_defined = some text here
ld_read_timestamp = Check type of data required
SELECT single CALLER_APPL
FROM TKETRPROT
INTO ld_caller_appl.
SELECT single CALLER_DETAIL
FROM TKETRPROT
INTO ld_caller_detail.
ld_ignore_valutyp = '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 RKE_READ_OBJECTS or its description.