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

Search SAP Function Modules

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

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

Function ISU_O_INSTLN_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_INSTLN_PBO'"INTERNAL: Prepares the CALL SUBSCREEN PBO
  EXPORTING
*  X_NOTEXTS = ' ' "

 IMPORTING
   Y_EANLD =  "
   Y_EANLSD =  "

CHANGING
   XY_OBJ =  "Object Data

TABLES
*  YT_EANLHD =  "

.

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_SAPLES30_001 IS-U: User-Defined Checks in Screen Fields
EXIT_SAPLES30_002 IS-U: User-Defined Preassignment of Screen Fields
EXIT_SAPLES30_003 IS-U: User Exit PBO: PBO for Customer Subscreen
EXIT_SAPLES30_004 IS-U: User Exit PAI_BEFORE: Prepares the CALL SUBSCREEN PAI
EXIT_SAPLES30_005 IS-U: User Exit PAI_AFTER: Closes the CALL SUBSCREEN PAI
EXIT_SAPLES30_006 IS-U: User Exit OPEN: Opens Customer Object Processing
EXIT_SAPLES30_007 IS-U: User Exit INPUT: Checks and Copies Entries on Customer Subscreen
EXIT_SAPLES30_008 IS-U: User Exit PREPARE_CLOSE: Prepares Closing of Customer Data
EXIT_SAPLES30_009 IS-U: User Exit ACTION: Actions of Customer Subscreen
EXIT_SAPLES30_010 IS-U: User Exit CLOSE: Ends Customer Data Processing
EXIT_SAPLES30_011 User Exit to Customer-Specific Authorization Check of Utility Installation

IMPORTING Parameters details for ISU_O_INSTLN_PBO

X_NOTEXTS -

Data type: REGEN-KENNZX
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_O_INSTLN_PBO

Y_EANLD -

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

Y_EANLSD -

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

CHANGING Parameters details for ISU_O_INSTLN_PBO

XY_OBJ - Object Data

Data type: ISU01_INSTLN
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISU_O_INSTLN_PBO

YT_EANLHD -

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

Copy and paste ABAP code example for ISU_O_INSTLN_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_INSTLN_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