CHTR_SET_OBJECT_TRIGGER SAP Function module

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

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

Pattern for FM CHTR_SET_OBJECT_TRIGGER - CHTR SET OBJECT TRIGGER

CALL FUNCTION 'CHTR_SET_OBJECT_TRIGGER' "
  EXPORTING
    object_type =               " chtr_object_type  CHT: object type
    object_key =                " chtr_object_key  CHT: Object Key
*   date = SY-DATUM             " chtr_date     CHT: Date
*   use_buffer = SPACE          " xfeld         Checkbox Field
*   i_update_task = SPACE       " xfeld
  EXCEPTIONS
    UNKNOWN_OBJECT_TYPE = 1     "
    INTERNAL_ERROR = 2          "
    .  "  CHTR_SET_OBJECT_TRIGGER

ABAP code example for Function Module CHTR_SET_OBJECT_TRIGGER

The ABAP code below is a full code listing to execute function module CHTR_SET_OBJECT_TRIGGER 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_object_type) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'CHTR_SET_OBJECT_TRIGGER'
  EXPORTING
    object_type =                ld_object_type
    object_key =                 ld_object_key
*   date =                       ld_date
*   use_buffer =                 ld_use_buffer
*   i_update_task =              ld_i_update_task
  EXCEPTIONS
    UNKNOWN_OBJECT_TYPE =        1
    INTERNAL_ERROR =             2
    .  "  CHTR_SET_OBJECT_TRIGGER

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
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_object_type
 
 TYPE CHTR_OBJECT_TYPE ,
ld_object_key
 
 TYPE CHTR_OBJECT_KEY ,
ld_date
 
 TYPE CHTR_DATE ,
ld_use_buffer
 
 TYPE XFELD ,
ld_i_update_task
 
 TYPE XFELD .


ld_object_type = 'Check type of data required'.
ld_object_key = 'Check type of data required'.
ld_date = 'Check type of data required'.
ld_use_buffer = 'Check type of data required'.
ld_i_update_task = 'Check type of data required'.