SAP Function Modules

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







OBJECT_MAINTENANCE_CALL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name OBJECT_MAINTENANCE_CALL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SCHL
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM OBJECT_MAINTENANCE_CALL - OBJECT MAINTENANCE CALL





CALL FUNCTION 'OBJECT_MAINTENANCE_CALL' "Extended help; for tables(F4) or find obj.,sub-obj.(F1) or transaction
* EXPORTING
*   objectname = SPACE          " objsub-objectname  Object
*   objecttype = SPACE          " objsub-objecttype  Object type
*   subobjname = SPACE          " objsub-subobjname  Sub-object name
*   tabname = SPACE             " dd02l-tabname  Table name
*   language = SY-LANGU         " spras
*   iv_enclosing_object = SPACE  " tabname
* TABLES
*   subobj_list_from_t100o =    " t100o
  EXCEPTIONS
    INTERFACE_NOT_CORRECT = 1   "               Interface filled incorrectly
    TRANSACTION_NOT_MAINTAINED = 2  "           Sub-objekt contains no transaction
    TRANSACTION_NOT_FOUND = 3   "               Sub-object contains non-existent transaction
    TABLE_NOT_ACTIV = 4         "               Table is not active in DDIC
    TABLE_NOT_FOUND = 5         "               Table was not found in object list
    SUBOBJECT_NOT_FOUND_IN_PROJECT = 6  "       Sub-obj. is not in the specified project
    SUBOBJECT_NOT_FOUND_IN_GUIDE = 7  "         Sub-object does not exist in the system
    OBJECT_NOT_FOUND_IN_PROJECT = 8  "          Object does not exist in the project
    OBJECT_NOT_FOUND_IN_GUIDE = 9  "            Object does not exist in the system
    TABLE_HAS_NO_OBJECT_IN_PROJECT = 10  "      Table is not maintained in project
    TABLE_HAS_NO_OBJECT_IN_GUIDE = 11  "        Table is not in object list
    OUTLINE_NOT_FOUND = 12      "               Structure not found
    CALL_TRANSACTION_RECURRING = 13  "          Recursive transaction call
    SYSTEM_FAILURE = 14         "               System locking error
    .  "  OBJECT_MAINTENANCE_CALL

ABAP code example for Function Module OBJECT_MAINTENANCE_CALL





The ABAP code below is a full code listing to execute function module OBJECT_MAINTENANCE_CALL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_subobj_list_from_t100o  TYPE STANDARD TABLE OF T100O,"TABLES PARAM
wa_subobj_list_from_t100o  LIKE LINE OF it_subobj_list_from_t100o .


SELECT single OBJECTNAME
FROM OBJSUB
INTO @DATA(ld_objectname).


SELECT single OBJECTTYPE
FROM OBJSUB
INTO @DATA(ld_objecttype).


SELECT single SUBOBJNAME
FROM OBJSUB
INTO @DATA(ld_subobjname).


SELECT single TABNAME
FROM DD02L
INTO @DATA(ld_tabname).

DATA(ld_language) = 'Check type of data required'.
DATA(ld_iv_enclosing_object) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_subobj_list_from_t100o to it_subobj_list_from_t100o. . CALL FUNCTION 'OBJECT_MAINTENANCE_CALL' * EXPORTING * objectname = ld_objectname * objecttype = ld_objecttype * subobjname = ld_subobjname * tabname = ld_tabname * language = ld_language * iv_enclosing_object = ld_iv_enclosing_object * TABLES * subobj_list_from_t100o = it_subobj_list_from_t100o EXCEPTIONS INTERFACE_NOT_CORRECT = 1 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 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 . " OBJECT_MAINTENANCE_CALL
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 8. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 9. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 10. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 11. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 12. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 13. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 14. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_objectname  TYPE OBJSUB-OBJECTNAME ,
it_subobj_list_from_t100o  TYPE STANDARD TABLE OF T100O ,
wa_subobj_list_from_t100o  LIKE LINE OF it_subobj_list_from_t100o,
ld_objecttype  TYPE OBJSUB-OBJECTTYPE ,
ld_subobjname  TYPE OBJSUB-SUBOBJNAME ,
ld_tabname  TYPE DD02L-TABNAME ,
ld_language  TYPE SPRAS ,
ld_iv_enclosing_object  TYPE TABNAME .


SELECT single OBJECTNAME
FROM OBJSUB
INTO ld_objectname.


"populate fields of struture and append to itab
append wa_subobj_list_from_t100o to it_subobj_list_from_t100o.

SELECT single OBJECTTYPE
FROM OBJSUB
INTO ld_objecttype.


SELECT single SUBOBJNAME
FROM OBJSUB
INTO ld_subobjname.


SELECT single TABNAME
FROM DD02L
INTO ld_tabname.

ld_language = 'Check type of data required'.
ld_iv_enclosing_object = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name OBJECT_MAINTENANCE_CALL or its description.