SAP RPY_DATAELEMENT_READ Function Module for









RPY_DATAELEMENT_READ is a standard rpy dataelement read 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 rpy dataelement read FM, simply by entering the name RPY_DATAELEMENT_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function RPY_DATAELEMENT_READ 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 'RPY_DATAELEMENT_READ'"
EXPORTING
* ACTIVATION_TYPE_I = 'M' "
DATAELEMENT_NAME = "
* LANGUAGE = SY-LANGU "
* WITH_DOCU = ' ' "
* DOCUTYPE = 'U' "

IMPORTING
DTEL_INF = "
ACTIVATION_TYPE_O = "

TABLES
* DOCU_TABLE_USER = "
* DOCU_TABLE_TECH = "

EXCEPTIONS
CANCELLED = 1 NOT_FOUND = 2 PERMISSION_ERROR = 3 ILLEGAL_TYPE = 4
.



IMPORTING Parameters details for RPY_DATAELEMENT_READ

ACTIVATION_TYPE_I -

Data type: DD04L-AS4LOCAL
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATAELEMENT_NAME -

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

LANGUAGE -

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

WITH_DOCU -

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

DOCUTYPE -

Data type: RGLIF-DOCUTYPE
Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RPY_DATAELEMENT_READ

DTEL_INF -

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

ACTIVATION_TYPE_O -

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

TABLES Parameters details for RPY_DATAELEMENT_READ

DOCU_TABLE_USER -

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

DOCU_TABLE_TECH -

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

EXCEPTIONS details

CANCELLED -

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

NOT_FOUND - Data element not found

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

PERMISSION_ERROR - User does not have display authorization

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

ILLEGAL_TYPE -

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

Copy and paste ABAP code example for RPY_DATAELEMENT_READ 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:
lv_dtel_inf  TYPE RPY_DTEL, "   
lv_cancelled  TYPE RPY_DTEL, "   
lt_docu_table_user  TYPE STANDARD TABLE OF RPY_OBJTAB, "   
lv_activation_type_i  TYPE DD04L-AS4LOCAL, "   'M'
lv_not_found  TYPE DD04L, "   
lt_docu_table_tech  TYPE STANDARD TABLE OF TLINE, "   
lv_dataelement_name  TYPE RPY_DTEL-DTELNAME, "   
lv_activation_type_o  TYPE DD04L-AS4LOCAL, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_permission_error  TYPE SY, "   
lv_with_docu  TYPE RGLIF-WITH_DOCU, "   ' '
lv_illegal_type  TYPE RGLIF, "   
lv_docutype  TYPE RGLIF-DOCUTYPE. "   'U'

  CALL FUNCTION 'RPY_DATAELEMENT_READ'  "
    EXPORTING
         ACTIVATION_TYPE_I = lv_activation_type_i
         DATAELEMENT_NAME = lv_dataelement_name
         LANGUAGE = lv_language
         WITH_DOCU = lv_with_docu
         DOCUTYPE = lv_docutype
    IMPORTING
         DTEL_INF = lv_dtel_inf
         ACTIVATION_TYPE_O = lv_activation_type_o
    TABLES
         DOCU_TABLE_USER = lt_docu_table_user
         DOCU_TABLE_TECH = lt_docu_table_tech
    EXCEPTIONS
        CANCELLED = 1
        NOT_FOUND = 2
        PERMISSION_ERROR = 3
        ILLEGAL_TYPE = 4
. " RPY_DATAELEMENT_READ




ABAP code using 7.40 inline data declarations to call FM RPY_DATAELEMENT_READ

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 AS4LOCAL FROM DD04L INTO @DATA(ld_activation_type_i).
DATA(ld_activation_type_i) = 'M'.
 
 
 
"SELECT single DTELNAME FROM RPY_DTEL INTO @DATA(ld_dataelement_name).
 
"SELECT single AS4LOCAL FROM DD04L INTO @DATA(ld_activation_type_o).
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
"SELECT single WITH_DOCU FROM RGLIF INTO @DATA(ld_with_docu).
DATA(ld_with_docu) = ' '.
 
 
"SELECT single DOCUTYPE FROM RGLIF INTO @DATA(ld_docutype).
DATA(ld_docutype) = 'U'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!