SAP APB_ISR_PROCESS_EVENT Function Module for ISR processing
APB_ISR_PROCESS_EVENT is a standard apb isr process event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ISR processing 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 apb isr process event FM, simply by entering the name APB_ISR_PROCESS_EVENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: APB_ISR_PROCESS
Program Name: SAPLAPB_ISR_PROCESS
Main Program: SAPLAPB_ISR_PROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function APB_ISR_PROCESS_EVENT 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 'APB_ISR_PROCESS_EVENT'"ISR processing.
EXPORTING
IV_SCENARIO = "Scenario
IV_MODE = "Mode
* IV_OBJECTID = "Object ID
* IV_EVENT = "Event
* IS_GENERAL_DATA = "General data
IMPORTING
EV_OBJECTID_OUT = "Object ID
ES_RETURN = "Return Parameter
ES_GENERAL_DATA = "General data
TABLES
T_DATA = "Form fields
T_ADDITIONAL_DATA = "Index, Name, Value of a field
* T_EXTERNAL_DATA = "application specific data
* T_MESSAGE_LIST = "Return parameter table
* T_UI_ATTRIBUTES = "UI Attributes
IMPORTING Parameters details for APB_ISR_PROCESS_EVENT
IV_SCENARIO - Scenario
Data type: APB_ISR_SCENARIOOptional: No
Call by Reference: No ( called with pass by value option)
IV_MODE - Mode
Data type: APB_ISR_MODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJECTID - Object ID
Data type: APB_ISR_OBJECTIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_EVENT - Event
Data type: APB_ISR_EVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_GENERAL_DATA - General data
Data type: APB_ISR_S_GENERAL_PARAMOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for APB_ISR_PROCESS_EVENT
EV_OBJECTID_OUT - Object ID
Data type: APB_ISR_OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
ES_RETURN - Return Parameter
Data type: BAPIRET1Optional: No
Call by Reference: No ( called with pass by value option)
ES_GENERAL_DATA - General data
Data type: APB_ISR_S_GENERAL_PARAMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for APB_ISR_PROCESS_EVENT
T_DATA - Form fields
Data type: APB_ISR_S_REQUESTDATAOptional: No
Call by Reference: Yes
T_ADDITIONAL_DATA - Index, Name, Value of a field
Data type: APB_ISR_T_SPECIAL_PARAMOptional: No
Call by Reference: Yes
T_EXTERNAL_DATA - application specific data
Data type: APB_ISR_T_SPECIAL_PARAMOptional: Yes
Call by Reference: Yes
T_MESSAGE_LIST - Return parameter table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
T_UI_ATTRIBUTES - UI Attributes
Data type: APB_ISR_T_UI_ATTRIBUTE_PARAMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for APB_ISR_PROCESS_EVENT 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: | ||||
| lt_t_data | TYPE STANDARD TABLE OF APB_ISR_S_REQUESTDATA, " | |||
| lv_iv_scenario | TYPE APB_ISR_SCENARIO, " | |||
| lv_ev_objectid_out | TYPE APB_ISR_OBJECTID, " | |||
| lv_iv_mode | TYPE APB_ISR_MODE, " | |||
| lv_es_return | TYPE BAPIRET1, " | |||
| lt_t_additional_data | TYPE STANDARD TABLE OF APB_ISR_T_SPECIAL_PARAM, " | |||
| lv_iv_objectid | TYPE APB_ISR_OBJECTID, " | |||
| lv_es_general_data | TYPE APB_ISR_S_GENERAL_PARAM, " | |||
| lt_t_external_data | TYPE STANDARD TABLE OF APB_ISR_T_SPECIAL_PARAM, " | |||
| lv_iv_event | TYPE APB_ISR_EVENT, " | |||
| lt_t_message_list | TYPE STANDARD TABLE OF BAPIRET2_T, " | |||
| lv_is_general_data | TYPE APB_ISR_S_GENERAL_PARAM, " | |||
| lt_t_ui_attributes | TYPE STANDARD TABLE OF APB_ISR_T_UI_ATTRIBUTE_PARAM. " |
|   CALL FUNCTION 'APB_ISR_PROCESS_EVENT' "ISR processing |
| EXPORTING | ||
| IV_SCENARIO | = lv_iv_scenario | |
| IV_MODE | = lv_iv_mode | |
| IV_OBJECTID | = lv_iv_objectid | |
| IV_EVENT | = lv_iv_event | |
| IS_GENERAL_DATA | = lv_is_general_data | |
| IMPORTING | ||
| EV_OBJECTID_OUT | = lv_ev_objectid_out | |
| ES_RETURN | = lv_es_return | |
| ES_GENERAL_DATA | = lv_es_general_data | |
| TABLES | ||
| T_DATA | = lt_t_data | |
| T_ADDITIONAL_DATA | = lt_t_additional_data | |
| T_EXTERNAL_DATA | = lt_t_external_data | |
| T_MESSAGE_LIST | = lt_t_message_list | |
| T_UI_ATTRIBUTES | = lt_t_ui_attributes | |
| . " APB_ISR_PROCESS_EVENT | ||
ABAP code using 7.40 inline data declarations to call FM APB_ISR_PROCESS_EVENT
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