ISHMED_ME_COMMIT_WORK SAP Function module

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

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

Pattern for FM ISHMED_ME_COMMIT_WORK - ISHMED ME COMMIT WORK

CALL FUNCTION 'ISHMED_ME_COMMIT_WORK' "
* EXPORTING
*   it_object =                 " ish_objectlist
*   it_identify =               " ish_t_identify_object
*   i_db_commit = ' '           " ish_on_off
  IMPORTING
    e_rc =                      " ish_method_rc  Return Code
    e_error_after_commit =      " ish_on_off
* CHANGING
*   cr_errorhandler =           " cl_ishmed_errorhandling  ISHMED: Class for Error Handling
    .  "  ISHMED_ME_COMMIT_WORK

ABAP code example for Function Module ISHMED_ME_COMMIT_WORK

The ABAP code below is a full code listing to execute function module ISHMED_ME_COMMIT_WORK 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_e_rc  
 
 TYPE ISH_METHOD_RC
,
ld_e_error_after_commit  
 
 TYPE ISH_ON_OFF
.


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

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

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

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

CALL FUNCTION 'ISHMED_ME_COMMIT_WORK'
* EXPORTING
*   it_object =                  ld_it_object
*   it_identify =                ld_it_identify
*   i_db_commit =                ld_i_db_commit
  IMPORTING
    e_rc =                       ld_e_rc
    e_error_after_commit =       ld_e_error_after_commit
* CHANGING
*   cr_errorhandler =            ld_cr_errorhandler
    .  "  ISHMED_ME_COMMIT_WORK

IF SY-SUBRC EQ 0.
  "All OK
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_cr_errorhandler
 
 TYPE CL_ISHMED_ERRORHANDLING ,
ld_e_rc
 
 TYPE ISH_METHOD_RC ,
ld_it_object
 
 TYPE ISH_OBJECTLIST ,
ld_e_error_after_commit
 
 TYPE ISH_ON_OFF ,
ld_it_identify
 
 TYPE ISH_T_IDENTIFY_OBJECT ,
ld_i_db_commit
 
 TYPE ISH_ON_OFF .


ld_cr_errorhandler = 'Check type of data required'.
ld_it_object = 'Check type of data required'.
ld_it_identify = 'Check type of data required'.
ld_i_db_commit = 'Check type of data required'.