SAP RV_MESSAGE_SELECT_SINGLE Function Module for NOTRANSL: Lesen einer Nachricht anhand ihres Schlüssels
RV_MESSAGE_SELECT_SINGLE is a standard rv message select single 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: Lesen einer Nachricht anhand ihres Schlüssels 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 rv message select single FM, simply by entering the name RV_MESSAGE_SELECT_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: VMSG
Program Name: SAPLVMSG
Main Program: SAPLVMSG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RV_MESSAGE_SELECT_SINGLE 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 'RV_MESSAGE_SELECT_SINGLE'"NOTRANSL: Lesen einer Nachricht anhand ihres Schlüssels.
EXPORTING
PI_NAST_KEY = "
IMPORTING
PE_NAST = "
EXCEPTIONS
RECORD_NOT_FOUND = 1
IMPORTING Parameters details for RV_MESSAGE_SELECT_SINGLE
PI_NAST_KEY -
Data type: NAST_KEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RV_MESSAGE_SELECT_SINGLE
PE_NAST -
Data type: NASTOptional: No
Call by Reference: Yes
EXCEPTIONS details
RECORD_NOT_FOUND - NAST entry not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RV_MESSAGE_SELECT_SINGLE 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_pe_nast | TYPE NAST, " | |||
| lv_pi_nast_key | TYPE NAST_KEY, " | |||
| lv_record_not_found | TYPE NAST_KEY. " |
|   CALL FUNCTION 'RV_MESSAGE_SELECT_SINGLE' "NOTRANSL: Lesen einer Nachricht anhand ihres Schlüssels |
| EXPORTING | ||
| PI_NAST_KEY | = lv_pi_nast_key | |
| IMPORTING | ||
| PE_NAST | = lv_pe_nast | |
| EXCEPTIONS | ||
| RECORD_NOT_FOUND = 1 | ||
| . " RV_MESSAGE_SELECT_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM RV_MESSAGE_SELECT_SINGLE
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.Search for further information about these or an SAP related objects