SAP EXIT_SAPLES30_001 Function Module for IS-U: User-Defined Checks in Screen Fields









EXIT_SAPLES30_001 is a standard exit saples30 001 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-Defined Checks in Screen Fields 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 001 FM, simply by entering the name EXIT_SAPLES30_001 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_001 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_001'"IS-U: User-Defined Checks in Screen Fields
  EXPORTING
   X_EANLSD =  "Screen Fields: Installation Transaction
   X_WMODE =  "Processing Type: 1=Display 2=Change 3=Create

 IMPORTING
   Y_FIELD =  "Field from Program
   Y_CURLINE =  "

TABLES
   XT_EANLHD =  "Table of Historical Fields in Installation Transaction

EXCEPTIONS
   INPUT_ERROR = 1
.



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_001

X_EANLSD - Screen Fields: Installation Transaction

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

X_WMODE - Processing Type: 1=Display 2=Change 3=Create

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

EXPORTING Parameters details for EXIT_SAPLES30_001

Y_FIELD - Field from Program

Data type: GFC_PRGFLD-FELDNAME
Optional: No
Call by Reference: Yes

Y_CURLINE -

Data type: SY-LINNO
Optional: No
Call by Reference: Yes

TABLES Parameters details for EXIT_SAPLES30_001

XT_EANLHD - Table of Historical Fields in Installation Transaction

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

EXCEPTIONS details

INPUT_ERROR - Error in Entry

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

Copy and paste ABAP code example for EXIT_SAPLES30_001 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_field  TYPE GFC_PRGFLD-FELDNAME, "   
lv_x_eanlsd  TYPE EANLSD, "   
lt_xt_eanlhd  TYPE STANDARD TABLE OF EANLHD, "   
lv_input_error  TYPE EANLHD, "   
lv_x_wmode  TYPE REGEN-WMODE, "   
lv_y_curline  TYPE SY-LINNO. "   

  CALL FUNCTION 'EXIT_SAPLES30_001'  "IS-U: User-Defined Checks in Screen Fields
    EXPORTING
         X_EANLSD = lv_x_eanlsd
         X_WMODE = lv_x_wmode
    IMPORTING
         Y_FIELD = lv_y_field
         Y_CURLINE = lv_y_curline
    TABLES
         XT_EANLHD = lt_xt_eanlhd
    EXCEPTIONS
        INPUT_ERROR = 1
. " EXIT_SAPLES30_001




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLES30_001

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.

"SELECT single FELDNAME FROM GFC_PRGFLD INTO @DATA(ld_y_field).
 
 
 
 
"SELECT single WMODE FROM REGEN INTO @DATA(ld_x_wmode).
 
"SELECT single LINNO FROM SY INTO @DATA(ld_y_curline).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!