SAP ALE_EDIT_CHECK Function Module for ALE: Test if customizing object can be maintained
ALE_EDIT_CHECK is a standard ale edit check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ALE: Test if customizing object can be maintained 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 ale edit check FM, simply by entering the name ALE_EDIT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCO
Program Name: SAPLSDCO
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_EDIT_CHECK 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 'ALE_EDIT_CHECK'"ALE: Test if customizing object can be maintained.
EXPORTING
OBJECTTYPE = "
OBJECTNAME = "
IMPORTING
SOMEKEYS_NOEDIT = "
EXCEPTIONS
NO_EDIT = 1 NO_CALL = 2
IMPORTING Parameters details for ALE_EDIT_CHECK
OBJECTTYPE -
Data type: OBJH-OBJECTTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTNAME -
Data type: OBJH-OBJECTNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ALE_EDIT_CHECK
SOMEKEYS_NOEDIT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_EDIT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALE_EDIT_CHECK 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_no_edit | TYPE STRING, " | |||
| lv_objecttype | TYPE OBJH-OBJECTTYPE, " | |||
| lv_somekeys_noedit | TYPE OBJH, " | |||
| lv_no_call | TYPE OBJH, " | |||
| lv_objectname | TYPE OBJH-OBJECTNAME. " |
|   CALL FUNCTION 'ALE_EDIT_CHECK' "ALE: Test if customizing object can be maintained |
| EXPORTING | ||
| OBJECTTYPE | = lv_objecttype | |
| OBJECTNAME | = lv_objectname | |
| IMPORTING | ||
| SOMEKEYS_NOEDIT | = lv_somekeys_noedit | |
| EXCEPTIONS | ||
| NO_EDIT = 1 | ||
| NO_CALL = 2 | ||
| . " ALE_EDIT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ALE_EDIT_CHECK
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.| "SELECT single OBJECTTYPE FROM OBJH INTO @DATA(ld_objecttype). | ||||
| "SELECT single OBJECTNAME FROM OBJH INTO @DATA(ld_objectname). | ||||
Search for further information about these or an SAP related objects