COM_IL_API_CHANGE SAP Function module

COM_IL_API_CHANGE 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 COM_IL_API_CHANGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: COM_IL_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM COM_IL_API_CHANGE - COM IL API CHANGE

CALL FUNCTION 'COM_IL_API_CHANGE' "
  EXPORTING
    iv_reltype =                " comt_il_reltype  Relationship Category
*   iv_no_change_doc =          " comt_il_change_doc
*   iv_enqmode = 'E'            " comt_il_enqmode  Lock Mode
*   iv_raise_exception = SPACE  " comt_il_raise_exception
    it_link_attr =              " table
*   iv_no_check = SPACE         " xfeld
  IMPORTING
    et_messages =               " comt_il_error_tab
  EXCEPTIONS
    LOCK_FAILED = 1             "
    .  "  COM_IL_API_CHANGE

ABAP code example for Function Module COM_IL_API_CHANGE

The ABAP code below is a full code listing to execute function module COM_IL_API_CHANGE 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:
ld_et_messages  
 
 TYPE COMT_IL_ERROR_TAB
.


DATA(ld_iv_reltype) = 'Check type of data required'.

DATA(ld_iv_no_change_doc) = 'Check type of data required'.

DATA(ld_iv_enqmode) = 'Check type of data required'.

DATA(ld_iv_raise_exception) = 'Check type of data required'.

DATA(ld_it_link_attr) = 'Check type of data required'.

DATA(ld_iv_no_check) = 'Check type of data required'.
.

CALL FUNCTION 'COM_IL_API_CHANGE'
  EXPORTING
    iv_reltype =                 ld_iv_reltype
*   iv_no_change_doc =           ld_iv_no_change_doc
*   iv_enqmode =                 ld_iv_enqmode
*   iv_raise_exception =         ld_iv_raise_exception
    it_link_attr =               ld_it_link_attr
*   iv_no_check =                ld_iv_no_check
  IMPORTING
    et_messages =                ld_et_messages
  EXCEPTIONS
    LOCK_FAILED =                1
    .  "  COM_IL_API_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_et_messages
 
 TYPE COMT_IL_ERROR_TAB ,
ld_iv_reltype
 
 TYPE COMT_IL_RELTYPE ,
ld_iv_no_change_doc
 
 TYPE COMT_IL_CHANGE_DOC ,
ld_iv_enqmode
 
 TYPE COMT_IL_ENQMODE ,
ld_iv_raise_exception
 
 TYPE COMT_IL_RAISE_EXCEPTION ,
ld_it_link_attr
 
 TYPE TABLE ,
ld_iv_no_check
 
 TYPE XFELD .


ld_iv_reltype = 'Check type of data required'.
ld_iv_no_change_doc = 'Check type of data required'.
ld_iv_enqmode = 'Check type of data required'.
ld_iv_raise_exception = 'Check type of data required'.
ld_it_link_attr = 'Check type of data required'.
ld_iv_no_check = 'Check type of data required'.