BM_OBJECT_SET_SYNCH SAP Function module - Set Deletion Indicator

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

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

Pattern for FM BM_OBJECT_SET_SYNCH - BM OBJECT SET SYNCH

CALL FUNCTION 'BM_OBJECT_SET_SYNCH' "Set Deletion Indicator
  EXPORTING
    i_object_type =             " bmobject-type  Object Type
    i_object_id =               " bmobject-id   Object key
*   i_new_synch = SPACE         " ufsynch       Synchronization flag
*   i_cico_reqno =              " rpygsgf-cico_reqno  Transfer Order Number
*   no_cico_dialog = SPACE      " bmt_flag
  IMPORTING
    e_object =                  " any
  EXCEPTIONS
    NOT_FOUND = 1               "
    NO_ACCESS_PERMISSION = 2    "
    DB_FAULT = 3                "
    .  "  BM_OBJECT_SET_SYNCH

ABAP code example for Function Module BM_OBJECT_SET_SYNCH

The ABAP code below is a full code listing to execute function module BM_OBJECT_SET_SYNCH 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_object  
 
 TYPE ANY
.



DATA(ld_i_object_type) = some text here


DATA(ld_i_object_id) = some text here

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


DATA(ld_i_cico_reqno) = some text here

DATA(ld_no_cico_dialog) = 'some text here'.
.

CALL FUNCTION 'BM_OBJECT_SET_SYNCH'
  EXPORTING
    i_object_type =              ld_i_object_type
    i_object_id =                ld_i_object_id
*   i_new_synch =                ld_i_new_synch
*   i_cico_reqno =               ld_i_cico_reqno
*   no_cico_dialog =             ld_no_cico_dialog
  IMPORTING
    e_object =                   ld_e_object
  EXCEPTIONS
    NOT_FOUND =                  1
    NO_ACCESS_PERMISSION =       2
    DB_FAULT =                   3
    .  "  BM_OBJECT_SET_SYNCH

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_e_object
 
 TYPE ANY ,
ld_i_object_type
 
 TYPE BMOBJECT-TYPE ,
ld_i_object_id
 
 TYPE BMOBJECT-ID ,
ld_i_new_synch
 
 TYPE UFSYNCH ,
ld_i_cico_reqno
 
 TYPE RPYGSGF-CICO_REQNO ,
ld_no_cico_dialog
 
 TYPE BMT_FLAG .



ld_i_object_type = some text here

ld_i_object_id = some text here
ld_i_new_synch = 'Check type of data required'.

ld_i_cico_reqno = some text here
ld_no_cico_dialog = 'some text here'.