SAP FTR_CORR_POPUP_ENQUEUE_EXIT Function Module for Confirmation Prompt in Case of Lock Errors in SWIFT Run
FTR_CORR_POPUP_ENQUEUE_EXIT is a standard ftr corr popup enqueue exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Confirmation Prompt in Case of Lock Errors in SWIFT Run 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 ftr corr popup enqueue exit FM, simply by entering the name FTR_CORR_POPUP_ENQUEUE_EXIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_CORR_TOOLS
Program Name: SAPLFTR_CORR_TOOLS
Main Program: SAPLFTR_CORR_TOOLS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_CORR_POPUP_ENQUEUE_EXIT 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 'FTR_CORR_POPUP_ENQUEUE_EXIT'"Confirmation Prompt in Case of Lock Errors in SWIFT Run.
EXPORTING
PI_BUKRS = "Company Code
PI_RFHA = "Financial Transaction
PI_USER = "SAP System, User Logon Name
IMPORTING
E_ANSWER = "Kennzeichen JA/NEIN
IMPORTING Parameters details for FTR_CORR_POPUP_ENQUEUE_EXIT
PI_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
PI_RFHA - Financial Transaction
Data type: TB_RFHAOptional: No
Call by Reference: Yes
PI_USER - SAP System, User Logon Name
Data type: SY-UNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FTR_CORR_POPUP_ENQUEUE_EXIT
E_ANSWER - Kennzeichen JA/NEIN
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_CORR_POPUP_ENQUEUE_EXIT 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_e_answer | TYPE STRING, " | |||
| lv_pi_bukrs | TYPE BUKRS, " | |||
| lv_pi_rfha | TYPE TB_RFHA, " | |||
| lv_pi_user | TYPE SY-UNAME. " |
|   CALL FUNCTION 'FTR_CORR_POPUP_ENQUEUE_EXIT' "Confirmation Prompt in Case of Lock Errors in SWIFT Run |
| EXPORTING | ||
| PI_BUKRS | = lv_pi_bukrs | |
| PI_RFHA | = lv_pi_rfha | |
| PI_USER | = lv_pi_user | |
| IMPORTING | ||
| E_ANSWER | = lv_e_answer | |
| . " FTR_CORR_POPUP_ENQUEUE_EXIT | ||
ABAP code using 7.40 inline data declarations to call FM FTR_CORR_POPUP_ENQUEUE_EXIT
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 UNAME FROM SY INTO @DATA(ld_pi_user). | ||||
Search for further information about these or an SAP related objects