SAP RPY_TRANSACTION_READ Function Module for
RPY_TRANSACTION_READ is a standard rpy transaction 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 transaction read FM, simply by entering the name RPY_TRANSACTION_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEUK
Program Name: SAPLSEUK
Main Program: SAPLSEUK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RPY_TRANSACTION_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_TRANSACTION_READ'".
EXPORTING
* TRANSACTION = "
* PROGRAM = "Program Name
* DYNPRO = "Screen Number
* TRANSACTION_TYPE = ' ' "
TABLES
* TCODES = "
* GUI_ATTRIBUTES = "Additional Attributes for TSTC
EXCEPTIONS
PERMISSION_ERROR = 1 CANCELLED = 2 NOT_FOUND = 3 OBJECT_NOT_FOUND = 4
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLSEUK_001 Exit Transaction Code Maintenance (Invisible Call)
EXIT_SAPLSEUK_002 Exit Transaction Code Maintenance
IMPORTING Parameters details for RPY_TRANSACTION_READ
TRANSACTION -
Data type: TSTC-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
PROGRAM - Program Name
Data type: TRDIR-NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
DYNPRO - Screen Number
Data type: D020S-DNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
TRANSACTION_TYPE -
Data type: RGLIF-DOCUTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RPY_TRANSACTION_READ
TCODES -
Data type: TSTCOptional: Yes
Call by Reference: No ( called with pass by value option)
GUI_ATTRIBUTES - Additional Attributes for TSTC
Data type: TSTCCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
PERMISSION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RPY_TRANSACTION_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: | ||||
| lt_tcodes | TYPE STANDARD TABLE OF TSTC, " | |||
| lv_transaction | TYPE TSTC-TCODE, " | |||
| lv_permission_error | TYPE TSTC, " | |||
| lv_program | TYPE TRDIR-NAME, " | |||
| lv_cancelled | TYPE TRDIR, " | |||
| lt_gui_attributes | TYPE STANDARD TABLE OF TSTCC, " | |||
| lv_dynpro | TYPE D020S-DNUM, " | |||
| lv_not_found | TYPE D020S, " | |||
| lv_object_not_found | TYPE D020S, " | |||
| lv_transaction_type | TYPE RGLIF-DOCUTYPE. " SPACE |
|   CALL FUNCTION 'RPY_TRANSACTION_READ' " |
| EXPORTING | ||
| TRANSACTION | = lv_transaction | |
| PROGRAM | = lv_program | |
| DYNPRO | = lv_dynpro | |
| TRANSACTION_TYPE | = lv_transaction_type | |
| TABLES | ||
| TCODES | = lt_tcodes | |
| GUI_ATTRIBUTES | = lt_gui_attributes | |
| EXCEPTIONS | ||
| PERMISSION_ERROR = 1 | ||
| CANCELLED = 2 | ||
| NOT_FOUND = 3 | ||
| OBJECT_NOT_FOUND = 4 | ||
| . " RPY_TRANSACTION_READ | ||
ABAP code using 7.40 inline data declarations to call FM RPY_TRANSACTION_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 TCODE FROM TSTC INTO @DATA(ld_transaction). | ||||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_program). | ||||
| "SELECT single DNUM FROM D020S INTO @DATA(ld_dynpro). | ||||
| "SELECT single DOCUTYPE FROM RGLIF INTO @DATA(ld_transaction_type). | ||||
| DATA(ld_transaction_type) | = ' '. | |||
Search for further information about these or an SAP related objects