SAP Function Modules

SM_CHANGEDOCUMENT_DELETE SAP Function module







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

Associated Function Group: SCD_SM
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SM_CHANGEDOCUMENT_DELETE - SM CHANGEDOCUMENT DELETE





CALL FUNCTION 'SM_CHANGEDOCUMENT_DELETE' "
  EXPORTING
*   iv_mandant_new = '000'      " mandt
*   changenumber_tab =          " cdchangenr_range_tab
*   date_of_change = '00000000'  " cdhdr-udate
    objectclass_tab =           " cdobjectcl_range_tab
*   objectid_tab =              " cdobjectv_range_tab
*   tablekey_tab =              " cdtabkey_range_tab
*   tablename_tab =             " cdtabname_range_tab
*   time_of_change = '000000'   " cdhdr-utime
*   username_tab =              " cdusername_range_tab
*   tablekey254_tab =           " cdtabkeylo_range_tab
*   keyguid_tab =               " cdsysuuid_range_tab
*   date_until = '99991231'     " cdhdr-udate
*   time_until = '235959'       " cdhdr-utime
*   commit_counter = '200'      " c
*   with_commit = SPACE         " c
*   keyguid_str_tab =           " cdsysuuid_range_tab
  IMPORTING
    es_cdsolmig =               " cdsolmig
  EXCEPTIONS
    NO_RANGES_FOR_DELETE = 1    "
    NO_DATA_DELETED = 2         "
    WRONG_DATE_OR_TIME = 3      "
    .  "  SM_CHANGEDOCUMENT_DELETE

ABAP code example for Function Module SM_CHANGEDOCUMENT_DELETE





The ABAP code below is a full code listing to execute function module SM_CHANGEDOCUMENT_DELETE 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_es_cdsolmig  TYPE CDSOLMIG .

DATA(ld_iv_mandant_new) = 'Check type of data required'.
DATA(ld_changenumber_tab) = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO @DATA(ld_date_of_change).

DATA(ld_objectclass_tab) = 'Check type of data required'.
DATA(ld_objectid_tab) = 'Check type of data required'.
DATA(ld_tablekey_tab) = 'Check type of data required'.
DATA(ld_tablename_tab) = 'Check type of data required'.

SELECT single UTIME
FROM CDHDR
INTO @DATA(ld_time_of_change).

DATA(ld_username_tab) = 'Check type of data required'.
DATA(ld_tablekey254_tab) = 'Check type of data required'.
DATA(ld_keyguid_tab) = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO @DATA(ld_date_until).


SELECT single UTIME
FROM CDHDR
INTO @DATA(ld_time_until).

DATA(ld_commit_counter) = 'Check type of data required'.
DATA(ld_with_commit) = 'Check type of data required'.
DATA(ld_keyguid_str_tab) = 'Check type of data required'. . CALL FUNCTION 'SM_CHANGEDOCUMENT_DELETE' EXPORTING * iv_mandant_new = ld_iv_mandant_new * changenumber_tab = ld_changenumber_tab * date_of_change = ld_date_of_change objectclass_tab = ld_objectclass_tab * objectid_tab = ld_objectid_tab * tablekey_tab = ld_tablekey_tab * tablename_tab = ld_tablename_tab * time_of_change = ld_time_of_change * username_tab = ld_username_tab * tablekey254_tab = ld_tablekey254_tab * keyguid_tab = ld_keyguid_tab * date_until = ld_date_until * time_until = ld_time_until * commit_counter = ld_commit_counter * with_commit = ld_with_commit * keyguid_str_tab = ld_keyguid_str_tab IMPORTING es_cdsolmig = ld_es_cdsolmig EXCEPTIONS NO_RANGES_FOR_DELETE = 1 NO_DATA_DELETED = 2 WRONG_DATE_OR_TIME = 3 . " SM_CHANGEDOCUMENT_DELETE
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 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_es_cdsolmig  TYPE CDSOLMIG ,
ld_iv_mandant_new  TYPE MANDT ,
ld_changenumber_tab  TYPE CDCHANGENR_RANGE_TAB ,
ld_date_of_change  TYPE CDHDR-UDATE ,
ld_objectclass_tab  TYPE CDOBJECTCL_RANGE_TAB ,
ld_objectid_tab  TYPE CDOBJECTV_RANGE_TAB ,
ld_tablekey_tab  TYPE CDTABKEY_RANGE_TAB ,
ld_tablename_tab  TYPE CDTABNAME_RANGE_TAB ,
ld_time_of_change  TYPE CDHDR-UTIME ,
ld_username_tab  TYPE CDUSERNAME_RANGE_TAB ,
ld_tablekey254_tab  TYPE CDTABKEYLO_RANGE_TAB ,
ld_keyguid_tab  TYPE CDSYSUUID_RANGE_TAB ,
ld_date_until  TYPE CDHDR-UDATE ,
ld_time_until  TYPE CDHDR-UTIME ,
ld_commit_counter  TYPE C ,
ld_with_commit  TYPE C ,
ld_keyguid_str_tab  TYPE CDSYSUUID_RANGE_TAB .

ld_iv_mandant_new = 'Check type of data required'.
ld_changenumber_tab = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO ld_date_of_change.

ld_objectclass_tab = 'Check type of data required'.
ld_objectid_tab = 'Check type of data required'.
ld_tablekey_tab = 'Check type of data required'.
ld_tablename_tab = 'Check type of data required'.

SELECT single UTIME
FROM CDHDR
INTO ld_time_of_change.

ld_username_tab = 'Check type of data required'.
ld_tablekey254_tab = 'Check type of data required'.
ld_keyguid_tab = 'Check type of data required'.

SELECT single UDATE
FROM CDHDR
INTO ld_date_until.


SELECT single UTIME
FROM CDHDR
INTO ld_time_until.

ld_commit_counter = 'Check type of data required'.
ld_with_commit = 'Check type of data required'.
ld_keyguid_str_tab = '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 SM_CHANGEDOCUMENT_DELETE or its description.