SAP EXIT_SAPLE30D_002 Function Module for Checks for Installation, Removal, and Replacement

Search SAP Function Modules

EXIT_SAPLE30D_002 is a standard exit saple30d 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 Checks for Installation, Removal, and Replacement 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 saple30d 002 FM, simply by entering the name EXIT_SAPLE30D_002 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLE30D_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_SAPLE30D_002'"Checks for Installation, Removal, and Replacement
  EXPORTING
   X_ACTION =  "Action in the work list for installation, etc. (IS-U)
   X_DISP_INPUT =  "Screen Data for Installation, Removal, and Replacement
   X_ZW_INPUT =  "Table Type: Register Data for Inst./Removal/Replacement

 IMPORTING
   Y_TABIX =  "Internal Tables, Current Line Index
   Y_CURFIELD =  "Cursor field

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_METER_CLOSE_RELATION Internal: Remove Allocation of Device to an Installation
ISU_METER_INSTALL Internal: Installation of Devices in Device Location and Installation
ISU_METER_RELATE Internal: Allocate Device to an Installation
ISU_METER_REMOVE Internal: Removal of Devices from Device Location and Installation
ISU_METER_REPLACE Internal: Replacement of Devices in Device Location and Installation
ISU_O_METER_INSTALL_INPUT Internal: Checks Input Data of Installation
ISU_O_METER_REMOVE_INPUT Internal: Checks Input Data of Removal
ISU_O_METER_REPLACE_INPUT Internal: Checks Input Data of Installation
ISU_O_WORKLIST_INSTALL_INPUT Internal: Checks Input Data of Work List
ISU_S_WORKLIST_INSTALL Internal: Install Worklist
ISU_S_WORKLIST_INSTALL_PROVIDE Internal: Provides Worklist for Installation/Removal/Replacement
ISU_WORKLIST_INSTALL_REFRESH

IMPORTING Parameters details for EXIT_SAPLE30D_002

X_ACTION - Action in the work list for installation, etc. (IS-U)

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

X_DISP_INPUT - Screen Data for Installation, Removal, and Replacement

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

X_ZW_INPUT - Table Type: Register Data for Inst./Removal/Replacement

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

EXPORTING Parameters details for EXIT_SAPLE30D_002

Y_TABIX - Internal Tables, Current Line Index

Data type: SYST-TABIX
Optional: No
Call by Reference: Yes

Y_CURFIELD - Cursor field

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

EXCEPTIONS details

INPUT_ERROR - Input error

Data type:
Optional: No
Call by Reference: Yes

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