SAP FPM_GET_REPLY_ASYNC Function Module for Check message delivery
FPM_GET_REPLY_ASYNC is a standard fpm get reply async SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check message delivery 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 fpm get reply async FM, simply by entering the name FPM_GET_REPLY_ASYNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPM_AMC
Program Name: SAPLFPM_AMC
Main Program: SAPLFPM_AMC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FPM_GET_REPLY_ASYNC 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 'FPM_GET_REPLY_ASYNC'"Check message delivery.
EXPORTING
IV_CHANNEL_EXT_ID = "Channel Extension ID
IV_MESSAGE_ID = "Message ID
IV_TRACKING_TIME = "Tracking Time (Seconds)
IV_TRACKED_RECIPIENTS = "Number of Tracked Recipients
IMPORTING
EV_MESSAGE_ID = "Message ID
EV_CONFIRMED = "Confirmation Flag
IMPORTING Parameters details for FPM_GET_REPLY_ASYNC
IV_CHANNEL_EXT_ID - Channel Extension ID
Data type: SYSUUID_C32Optional: No
Call by Reference: No ( called with pass by value option)
IV_MESSAGE_ID - Message ID
Data type: SYSUUID_C32Optional: No
Call by Reference: No ( called with pass by value option)
IV_TRACKING_TIME - Tracking Time (Seconds)
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
IV_TRACKED_RECIPIENTS - Number of Tracked Recipients
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FPM_GET_REPLY_ASYNC
EV_MESSAGE_ID - Message ID
Data type: CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
EV_CONFIRMED - Confirmation Flag
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FPM_GET_REPLY_ASYNC 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_ev_message_id | TYPE CHAR32, " | |||
| lv_iv_channel_ext_id | TYPE SYSUUID_C32, " | |||
| lv_ev_confirmed | TYPE BOOLE_D, " | |||
| lv_iv_message_id | TYPE SYSUUID_C32, " | |||
| lv_iv_tracking_time | TYPE I, " | |||
| lv_iv_tracked_recipients | TYPE I. " |
|   CALL FUNCTION 'FPM_GET_REPLY_ASYNC' "Check message delivery |
| EXPORTING | ||
| IV_CHANNEL_EXT_ID | = lv_iv_channel_ext_id | |
| IV_MESSAGE_ID | = lv_iv_message_id | |
| IV_TRACKING_TIME | = lv_iv_tracking_time | |
| IV_TRACKED_RECIPIENTS | = lv_iv_tracked_recipients | |
| IMPORTING | ||
| EV_MESSAGE_ID | = lv_ev_message_id | |
| EV_CONFIRMED | = lv_ev_confirmed | |
| . " FPM_GET_REPLY_ASYNC | ||
ABAP code using 7.40 inline data declarations to call FM FPM_GET_REPLY_ASYNC
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