SAP EXIT_SAPLE30B_001 Function Module for Device replacement: Permissibility check

Search SAP Function Modules

EXIT_SAPLE30B_001 is a standard exit saple30b 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 Device replacement: Permissibility check 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 saple30b 001 FM, simply by entering the name EXIT_SAPLE30B_001 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLE30B_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_SAPLE30B_001'"Device replacement: Permissibility check
  EXPORTING
   X_EQUI_OLD =  "Work area: V_EGER of device to be removed
   X_EQUI_NEW =  "Work area: V_EGER of device to be installed
   X_MATNR_OLD =  "Work area: Device category of device to be removed
   X_MATNR_NEW =  "Work area: Device category of device to be installed
   X_DATE =  "Replacement date
   X_NO_DIALOG =  "Flag: Not in dialog mode

EXCEPTIONS
   NOT_ALLOWED = 1 

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISU_O_METER_WL_CHECK Private: Cross-Checks for Device Set
ISU_O_METER_WL_CLOSE Private: Closes a Device of Work List for Installation/Removal/Replacement
ISU_O_METER_WL_CORRECT_ZW Private: Fill Register with Current Logical Register
ISU_O_METER_WL_OPEN Private: Opens a Device of Work List for Installation/Removal/Replacement
ISU_O_WORKLIST_INSTALL_CLOSE Private: Closes Work List for Installation/Removal/Replacement
ISU_O_WORKLIST_INSTALL_OPEN Private: Opens Work List for Installation/Removal/Replacement

IMPORTING Parameters details for EXIT_SAPLE30B_001

X_EQUI_OLD - Work area: V_EGER of device to be removed

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

X_EQUI_NEW - Work area: V_EGER of device to be installed

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

X_MATNR_OLD - Work area: Device category of device to be removed

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

X_MATNR_NEW - Work area: Device category of device to be installed

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

X_DATE - Replacement date

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

X_NO_DIALOG - Flag: Not in dialog mode

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

EXCEPTIONS details

NOT_ALLOWED - Replacement not permitted

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

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