SAP FPRL_LOG_ITEM_READ Function Module for Read item log
FPRL_LOG_ITEM_READ is a standard fprl log item read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read item log 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 fprl log item read FM, simply by entering the name FPRL_LOG_ITEM_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPRL_LOG_DATA
Program Name: SAPLFPRL_LOG_DATA
Main Program: SAPLFPRL_LOG_DATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FPRL_LOG_ITEM_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 'FPRL_LOG_ITEM_READ'"Read item log.
EXPORTING
IS_ITEM_KEY = "Payment release: Key: Financial Accounting Document Segment
* I_FIELD_NAME = "Payment release: Field name
IMPORTING
ET_LOG = "Payment Release: Log
IMPORTING Parameters details for FPRL_LOG_ITEM_READ
IS_ITEM_KEY - Payment release: Key: Financial Accounting Document Segment
Data type: BSEG_KEYOptional: No
Call by Reference: Yes
I_FIELD_NAME - Payment release: Field name
Data type: FPRL_FIELD_NAMEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FPRL_LOG_ITEM_READ
ET_LOG - Payment Release: Log
Data type: FPRLT_LOGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPRL_LOG_ITEM_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_et_log | TYPE FPRLT_LOG, " | |||
| lv_is_item_key | TYPE BSEG_KEY, " | |||
| lv_i_field_name | TYPE FPRL_FIELD_NAME. " |
|   CALL FUNCTION 'FPRL_LOG_ITEM_READ' "Read item log |
| EXPORTING | ||
| IS_ITEM_KEY | = lv_is_item_key | |
| I_FIELD_NAME | = lv_i_field_name | |
| IMPORTING | ||
| ET_LOG | = lv_et_log | |
| . " FPRL_LOG_ITEM_READ | ||
ABAP code using 7.40 inline data declarations to call FM FPRL_LOG_ITEM_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.Search for further information about these or an SAP related objects