SAP FPCR_REVERSE_UPDATE_CASE_1042 Function Module for
FPCR_REVERSE_UPDATE_CASE_1042 is a standard fpcr reverse update case 1042 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 fpcr reverse update case 1042 FM, simply by entering the name FPCR_REVERSE_UPDATE_CASE_1042 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPCR_REVERSE_UPDATE_CASE
Program Name: SAPLFPCR_REVERSE_UPDATE_CASE
Main Program: SAPLFPCR_REVERSE_UPDATE_CASE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FPCR_REVERSE_UPDATE_CASE_1042 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 'FPCR_REVERSE_UPDATE_CASE_1042'".
EXPORTING
I_RF05R = "
TABLES
T_XRAGL = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FPCR_REVERSE_UPDATE_CASE_1042
I_RF05R -
Data type: RF05ROptional: No
Call by Reference: Yes
TABLES Parameters details for FPCR_REVERSE_UPDATE_CASE_1042
T_XRAGL -
Data type: RAGL1Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPCR_REVERSE_UPDATE_CASE_1042 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_error | TYPE STRING, " | |||
| lv_i_rf05r | TYPE RF05R, " | |||
| lt_t_xragl | TYPE STANDARD TABLE OF RAGL1. " |
|   CALL FUNCTION 'FPCR_REVERSE_UPDATE_CASE_1042' " |
| EXPORTING | ||
| I_RF05R | = lv_i_rf05r | |
| TABLES | ||
| T_XRAGL | = lt_t_xragl | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FPCR_REVERSE_UPDATE_CASE_1042 | ||
ABAP code using 7.40 inline data declarations to call FM FPCR_REVERSE_UPDATE_CASE_1042
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