SAP OBJECT_MAINTENANCE_CALL Function Module for Extended help; for tables(F4) or find obj.,sub-obj.(F1) or transaction

Search SAP Function Modules

OBJECT_MAINTENANCE_CALL is a standard object maintenance call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extended help; for tables(F4) or find obj.,sub-obj.(F1) or transaction 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 call FM, simply by entering the name OBJECT_MAINTENANCE_CALL 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): Remote-Enabled
Update:

Function OBJECT_MAINTENANCE_CALL 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_CALL'"Extended help; for tables(F4) or find obj.,sub-obj.(F1) or transaction
  EXPORTING
*  OBJECTNAME = ' ' "Object
*  OBJECTTYPE = ' ' "Object type
*  SUBOBJNAME = ' ' "Sub-object name
*  TABNAME = ' ' "Table name
*  LANGUAGE = SY-LANGU "
*  IV_ENCLOSING_OBJECT = ' ' "

TABLES
*  SUBOBJ_LIST_FROM_T100O =  "

EXCEPTIONS
   INTERFACE_NOT_CORRECT = 1    TABLE_HAS_NO_OBJECT_IN_PROJECT = 10    TABLE_HAS_NO_OBJECT_IN_GUIDE = 11    OUTLINE_NOT_FOUND = 12    CALL_TRANSACTION_RECURRING = 13    SYSTEM_FAILURE = 14    TRANSACTION_NOT_MAINTAINED = 2    TRANSACTION_NOT_FOUND = 3    TABLE_NOT_ACTIV = 4    TABLE_NOT_FOUND = 5    SUBOBJECT_NOT_FOUND_IN_PROJECT = 6    SUBOBJECT_NOT_FOUND_IN_GUIDE = 7    OBJECT_NOT_FOUND_IN_PROJECT = 8    OBJECT_NOT_FOUND_IN_GUIDE = 9 

.

IMPORTING Parameters details for OBJECT_MAINTENANCE_CALL

OBJECTNAME - Object

Data type: OBJSUB-OBJECTNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECTTYPE - Object type

Data type: OBJSUB-OBJECTTYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUBOBJNAME - Sub-object name

Data type: OBJSUB-SUBOBJNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABNAME - Table name

Data type: DD02L-TABNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ENCLOSING_OBJECT -

Data type: TABNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for OBJECT_MAINTENANCE_CALL

SUBOBJ_LIST_FROM_T100O -

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

EXCEPTIONS details

INTERFACE_NOT_CORRECT - Interface filled incorrectly

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

TABLE_HAS_NO_OBJECT_IN_PROJECT - Table is not maintained in project

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

TABLE_HAS_NO_OBJECT_IN_GUIDE - Table is not in object list

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

OUTLINE_NOT_FOUND - Structure not found

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

CALL_TRANSACTION_RECURRING - Recursive transaction call

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

SYSTEM_FAILURE - System locking error

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

TRANSACTION_NOT_MAINTAINED - Sub-objekt contains no transaction

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

TRANSACTION_NOT_FOUND - Sub-object contains non-existent transaction

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

TABLE_NOT_ACTIV - Table is not active in DDIC

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)

SUBOBJECT_NOT_FOUND_IN_PROJECT - Sub-obj. is not in the specified project

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

SUBOBJECT_NOT_FOUND_IN_GUIDE - Sub-object does not exist in the system

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

OBJECT_NOT_FOUND_IN_PROJECT - Object does not exist in the project

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

OBJECT_NOT_FOUND_IN_GUIDE - Object does not exist in the system

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

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

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