SAP EXIT_SAPLES30_003 Function Module for IS-U: User Exit PBO: PBO for Customer Subscreen

Search SAP Function Modules

EXIT_SAPLES30_003 is a standard exit saples30 003 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U: User Exit PBO: PBO for Customer Subscreen 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 exit saples30 003 FM, simply by entering the name EXIT_SAPLES30_003 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLES30_003 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 'EXIT_SAPLES30_003'"IS-U: User Exit PBO: PBO for Customer Subscreen
  EXPORTING
   X_SUB_OBJ =  "Object Data of Subobject

CHANGING
   XY_EANLSD =  "Screen Fields: Installation Transaction

TABLES
   T_EANLHD =  "Table of Historical Fields in Installation Transaction

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISU_O_INSTLN_ACTION INTERNAL: Actions of Subscreens
ISU_O_INSTLN_CLOSE INTERNAL: Exits Object Processing
ISU_O_INSTLN_INPUT INTERNAL: Checks and Transfers Entries
ISU_O_INSTLN_INPUT_ INTERNAL: Checks and Transfers Entries
ISU_O_INSTLN_INPUT_AUTO INTERNAL: Checks and Adopts Automation Data
ISU_O_INSTLN_OPEN INTERNAL: Opens Processing of an Object
ISU_O_INSTLN_PAI_AFTER INTERNAL: Closes the CALL SUBSCREEN PAI
ISU_O_INSTLN_PAI_BEFORE INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_INSTLN_PBO INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_INSTLN_PBO_AFTER INTERNAL: Closes CALL SUBSCREEN PBO
ISU_O_INSTLN_PREPARE_CLOSE INTERNAL: Prepare Object Closing
ISU_S_INSTLN_CHANGE INTERNAL: Change an Installation
ISU_S_INSTLN_CREATE INTERNAL: Create an Installation
ISU_S_INSTLN_DISPLAY INTERNAL: Display an Installation
ISU_S_INSTLN_PROVIDE INTERNAL: Prepares an Installation for Processing

IMPORTING Parameters details for EXIT_SAPLES30_003

X_SUB_OBJ - Object Data of Subobject

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

CHANGING Parameters details for EXIT_SAPLES30_003

XY_EANLSD - Screen Fields: Installation Transaction

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

TABLES Parameters details for EXIT_SAPLES30_003

T_EANLHD - Table of Historical Fields in Installation Transaction

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

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

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