SAP EXIT_SAPLEL40_002 Function Module for Display Additional Fields at Device Location Level
EXIT_SAPLEL40_002 is a standard exit saplel40 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 Display Additional Fields at Device Location Level 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 saplel40 002 FM, simply by entering the name EXIT_SAPLEL40_002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XEL4
Program Name: SAPLXEL4
Main Program: SAPLXEL4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLEL40_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_SAPLEL40_002'"Display Additional Fields at Device Location Level.
EXPORTING
X_DEVLOC = "Device Location
* X_OBJ = "
IMPORTING
Y_ADDITIONAL_OUTPUT = "General Hierarchy Display: Additional Attributes
EXCEPTIONS
ERROR_MESSAGE = 1
Related IDocs
Below is a list of IDoc processing function modules and the associated IDocs this Function user exits is relevant for.ISU_IDOC_INPUT_ISU_EL40 - SAP IDoc ISU_EL40
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_DB_ELWEG_LOG_SELECT INTERNAL: Read ELWEG_LOG (Mass Access)
ISU_DB_ELWEG_SELECT INTERNAL: Read ELWEG of a MR Unit (Mass Access)
ISU_DB_ELWEG_SINGLE INTERNAL: Read ELWEG (Direct Access)
ISU_ELWEG_HIERARCHY_BUILD PRIVATE: Create Hierarchy for Street Route
ISU_O_STREET_ROUTE_ACTION INTERNAL: Actions of Object
ISU_O_STREET_ROUTE_CLOSE INTERNAL: Ends Processing of Street Route
ISU_O_STREET_ROUTE_OPEN INTERNAL: Opens Instance of Class for Street Route
ISU_O_STREET_ROUTE_PREP_CLOSE INTERNAL: PREPARE Module for Street Route
ISU_STREET_ROUTE_SCREEN PRIVATE: 'Dynpro' for Street Route Display
ISU_STREET_ROUTE_SCREEN_TEST Test
ISU_STREET_ROUTE_SCREEN_TEST1 Test
ISU_S_STREET_ROUTE_CHANGE INTERNAL: Maintain Street Route
ISU_S_STREET_ROUTE_CLEAR INTERNAL: Clear Street Route of Obsolete Device
ISU_S_STREET_ROUTE_CREATE INTERNAL: Create a Street Route
ISU_S_STREET_ROUTE_DELETE INTERNAL: Delete a Street Route
ISU_S_STREET_ROUTE_DISPLAY INTERNAL: Display a Street Route
ISU_S_STREET_ROUTE_PROVIDE INTERNAL: Prepare a Street Route
IMPORTING Parameters details for EXIT_SAPLEL40_002
X_DEVLOC - Device Location
Data type: EGPLOptional: No
Call by Reference: Yes
X_OBJ -
Data type: ISU17_SR_DATAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for EXIT_SAPLEL40_002
Y_ADDITIONAL_OUTPUT - General Hierarchy Display: Additional Attributes
Data type: STREETROUTE_CUSTOMER_TEXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_MESSAGE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLEL40_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.| DATA: | ||||
| lv_x_devloc | TYPE EGPL, " | |||
| lv_error_message | TYPE EGPL, " | |||
| lv_y_additional_output | TYPE STREETROUTE_CUSTOMER_TEXT, " | |||
| lv_x_obj | TYPE ISU17_SR_DATA. " |
|   CALL FUNCTION 'EXIT_SAPLEL40_002' "Display Additional Fields at Device Location Level |
| EXPORTING | ||
| X_DEVLOC | = lv_x_devloc | |
| X_OBJ | = lv_x_obj | |
| IMPORTING | ||
| Y_ADDITIONAL_OUTPUT | = lv_y_additional_output | |
| EXCEPTIONS | ||
| ERROR_MESSAGE = 1 | ||
| . " EXIT_SAPLEL40_002 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLEL40_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.See full list of SAP IDocs
See full list of SAP Function Modules
Search for further information about these or an SAP related objects