SAP ISU_O_DEVICE_PBO Function Module for INTERNAL: Prepares the CALL SUBSCREEN PBO

Search SAP Function Modules

ISU_O_DEVICE_PBO is a standard isu o device pbo 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: Prepares the 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 device pbo FM, simply by entering the name ISU_O_DEVICE_PBO into the relevant SAP transaction such as SE37 or SE38.

Function Group: E10R
Program Name: SAPLE10R
Main Program: SAPLE10R
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_O_DEVICE_PBO 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_DEVICE_PBO'"INTERNAL: Prepares the CALL SUBSCREEN PBO
  EXPORTING
*  X_MODE = 'A' "Bearbeitungsmodus für das IS-U Gerät
*  X_REFMATNR = ' ' "Material Number
*  X_REFSERNR = ' ' "Device

CHANGING
   XY_V_EQUI =  "Equipment structure

EXCEPTIONS
   OBJECT_NOT_FOUND = 1    DATA_ERROR = 2 

.

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_SAPLE10R_001 User exit: IS-U Data Checks for Goods Receipt/Device Creation
EXIT_SAPLE10R_002 User exit: Preassignment of data for dialog box during device creation
EXIT_SAPLE10R_003 User Exit: Device Data Check for Changes to Device

IMPORTING Parameters details for ISU_O_DEVICE_PBO

X_MODE - Bearbeitungsmodus für das IS-U Gerät

Data type: SY-FTYPE
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_REFMATNR - Material Number

Data type: MATNR
Default: SPACE
Optional: Yes
Call by Reference: Yes

X_REFSERNR - Device

Data type: GERAET
Default: SPACE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ISU_O_DEVICE_PBO

XY_V_EQUI - Equipment structure

Data type: V_EQUI
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OBJECT_NOT_FOUND - Keine Gerätedaten gefunden

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATA_ERROR - Fehler bei den übergebenen Daten

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_O_DEVICE_PBO 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.

ABAP code using 7.40 inline data declarations to call FM ISU_O_DEVICE_PBO

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