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

Search SAP Function Modules

EXIT_SAPLE20A_001 is a standard exit saple20a 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 saple20a 001 FM, simply by entering the name EXIT_SAPLE20A_001 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLE20A_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_SAPLE20A_001'"IS-U: User-Defined Checks in Screen Fields
  EXPORTING
   X_RE20A =  "Screen Fields for General Rate Cat. Header Data
   X_WMODE =  "Processing Mode (1 = Display, 2 = Change, 3 = Create...)

 IMPORTING
   Y_FIELD =  "Name of a Screen Element
   Y_DYNNR =  "ABAP Program, Number of Current Screen

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_RATE_CAT_ACTION INTERNAL: Subscreen Actions
ISU_O_RATE_CAT_CLOSE INTERNAL: Ends Processing of Rate Category
ISU_O_RATE_CAT_OPEN INTERNAL: Opens Processing of Rate Category
ISU_O_RATE_CAT_PREPARE_CLOSE INTERNAL: Prepare Object Closing
ISU_RATE_CAT_CHECK_SINGLE IS-U: Consistency Check of Single Rate Category
ISU_RATE_CAT_USAGE INTERNAL: Where-Used List for Rate Category
ISU_SINGLE_CUSTOM_EXIST_CHECK IS-U: Existency Check for Individual Customizing
ISU_S_RATE_CAT_CHANGE INTERNAL: Change Rate Category
ISU_S_RATE_CAT_CREATE INTERNAL: Create Rate Category
ISU_S_RATE_CAT_DELETE INTERNAL: Delete Rate Category
ISU_S_RATE_CAT_DISPLAY INTERNAL: Display Rate Category
ISU_S_RATE_CAT_PROVIDE INTERNAL: Prepares an Object for Processing

IMPORTING Parameters details for EXIT_SAPLE20A_001

X_RE20A - Screen Fields for General Rate Cat. Header Data

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

X_WMODE - Processing Mode (1 = Display, 2 = Change, 3 = Create...)

Data type: REGEN-WMODE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EXIT_SAPLE20A_001

Y_FIELD - Name of a Screen Element

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

Y_DYNNR - ABAP Program, Number of Current Screen

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

EXCEPTIONS details

INPUT_ERROR - Error during Entry

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLE20A_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.

Search for further information about these or an SAP related objects