SAP EXIT_SAPLES20_002 Function Module for IS-U: User-Defined Preassignment of Screen Fields

Search SAP Function Modules

EXIT_SAPLES20_002 is a standard exit saples20 002 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 Preassignment of 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 saples20 002 FM, simply by entering the name EXIT_SAPLES20_002 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLES20_002 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_SAPLES20_002'"IS-U: User-Defined Preassignment of Screen Fields
  EXPORTING
   X_WMODE =  "Processing Type 1=Disp 2=Chng 3=Create
   X_EVERD =  "Screen Fields for Contract Transaction

 IMPORTING
   Y_EVERD =  "Screen Fields for Contract 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_ARCH_READ_EVER
ISU_CONTRACT_CHECK_LOCK_REMOTE
ISU_EVERH_DATE_AUTO_PREPARE Determine Automatic Data for Date Changes
ISU_EVER_FKLOCK2_SAMPLE_9570 Processing Locks for FKLOCK2
ISU_F4_ABSZYK_EXIT Display Possible Input Values for Field ABSZYK_EXIT
ISU_O_CONTRACT_ACTION INTERNAL: Subscreen Actions
ISU_O_CONTRACT_CLOSE INTERNAL: End Processing for a Contract
ISU_O_CONTRACT_INPUT INTERNAL: Checks for Fields of Structure EVERA (General Contract Fields)
ISU_O_CONTRACT_OPEN INTERNAL: Opens Processing of a Contract
ISU_O_CONTRACT_PAI_AFTER INTERNAL: Closes the CALL SUBSCREEN PAI
ISU_O_CONTRACT_PAI_BEFORE INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_CONTRACT_PAI_MOD_SAVE INTERNAL: Transfer Business Partner to Contract Acct Object Before Saving
ISU_O_CONTRACT_PBO INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_CONTRACT_PBOMICRT INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_CONTRACT_PREPARE_CLOSE INTERNAL: Prepares for Closing of Contract
ISU_S_CONTRACT_CHANGE INTERNAL: Change a Contract
ISU_S_CONTRACT_CREATE INTERNAL: Create a Contract
ISU_S_CONTRACT_DISPLAY INTERNAL: Display a Contract
ISU_S_CONTRACT_DISPLAY_ARCHIVE
ISU_S_CONTRACT_PROVIDE INTERNAL: Prepares a Contract for Processing

IMPORTING Parameters details for EXIT_SAPLES20_002

X_WMODE - Processing Type 1=Disp 2=Chng 3=Create

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

X_EVERD - Screen Fields for Contract Transaction

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

EXPORTING Parameters details for EXIT_SAPLES20_002

Y_EVERD - Screen Fields for Contract Transaction

Data type: EVERD
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_SAPLES20_002 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_SAPLES20_002

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