SAP OBJECT_MAINTENANCE_CHECK Function Module for Check whether the table can be maintained under object
OBJECT_MAINTENANCE_CHECK is a standard object maintenance 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 Check whether the table can be maintained under object 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 object maintenance check FM, simply by entering the name OBJECT_MAINTENANCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCHL
Program Name: SAPLSCHL
Main Program: SAPLSCHL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_MAINTENANCE_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 'OBJECT_MAINTENANCE_CHECK'"Check whether the table can be maintained under object.
EXPORTING
TABNAME = "Table name
EXCEPTIONS
TABLE_NOT_ACTIV = 1 TABLE_NOT_FOUND = 2
IMPORTING Parameters details for OBJECT_MAINTENANCE_CHECK
TABNAME - Table name
Data type: DD02L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TABLE_NOT_ACTIV -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_FOUND - Table was not found in object list
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OBJECT_MAINTENANCE_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_tabname | TYPE DD02L-TABNAME, " | |||
| lv_table_not_activ | TYPE DD02L, " | |||
| lv_table_not_found | TYPE DD02L. " |
|   CALL FUNCTION 'OBJECT_MAINTENANCE_CHECK' "Check whether the table can be maintained under object |
| EXPORTING | ||
| TABNAME | = lv_tabname | |
| EXCEPTIONS | ||
| TABLE_NOT_ACTIV = 1 | ||
| TABLE_NOT_FOUND = 2 | ||
| . " OBJECT_MAINTENANCE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM OBJECT_MAINTENANCE_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 TABNAME FROM DD02L INTO @DATA(ld_tabname). | ||||
Search for further information about these or an SAP related objects