SAP ISU_O_DEVICEMOD_PBO_AFTER Function Module for INTERNAL: Closes CALL SUBSCREEN PBO
ISU_O_DEVICEMOD_PBO_AFTER is a standard isu o devicemod pbo after SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Closes CALL SUBSCREEN PBO 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 isu o devicemod pbo after FM, simply by entering the name ISU_O_DEVICEMOD_PBO_AFTER into the relevant SAP transaction such as SE37 or SE38.
Function Group: EG42
Program Name: SAPLEG42
Main Program: SAPLEG42
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_O_DEVICEMOD_PBO_AFTER 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 'ISU_O_DEVICEMOD_PBO_AFTER'"INTERNAL: Closes CALL SUBSCREEN PBO.
IMPORTING
Y_OBJ = "Object Data
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLEG42_001 Device Modification: Device and Register Data afer Modification
EXIT_SAPLEG42_002 Check Device Info Record, Device Data, and Register Data
EXPORTING Parameters details for ISU_O_DEVICEMOD_PBO_AFTER
Y_OBJ - Object Data
Data type: ISU42_DEVMODOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_O_DEVICEMOD_PBO_AFTER 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_y_obj | TYPE ISU42_DEVMOD. " |
|   CALL FUNCTION 'ISU_O_DEVICEMOD_PBO_AFTER' "INTERNAL: Closes CALL SUBSCREEN PBO |
| IMPORTING | ||
| Y_OBJ | = lv_y_obj | |
| . " ISU_O_DEVICEMOD_PBO_AFTER | ||
ABAP code using 7.40 inline data declarations to call FM ISU_O_DEVICEMOD_PBO_AFTER
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