ISU_O_TRIGGER_INPUT SAP Function module - INTERNAL: Checks and Transfers Entries

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

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

Pattern for FM ISU_O_TRIGGER_INPUT - ISU O TRIGGER INPUT

CALL FUNCTION 'ISU_O_TRIGGER_INPUT' "INTERNAL: Checks and Transfers Entries
  EXPORTING
    x_etrgd =                   " etrgd
  CHANGING
    xy_obj =                    " isu17_trigger  Object Data
  EXCEPTIONS
    INPUT_ERROR = 1             "               Entry is not allowed
    .  "  ISU_O_TRIGGER_INPUT

ABAP code example for Function Module ISU_O_TRIGGER_INPUT

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

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

CALL FUNCTION 'ISU_O_TRIGGER_INPUT'
  EXPORTING
    x_etrgd =                    ld_x_etrgd
  CHANGING
    xy_obj =                     ld_xy_obj
  EXCEPTIONS
    INPUT_ERROR =                1
    .  "  ISU_O_TRIGGER_INPUT

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_xy_obj
 
 TYPE ISU17_TRIGGER ,
ld_x_etrgd
 
 TYPE ETRGD .


ld_xy_obj = 'Check type of data required'.
ld_x_etrgd = 'Check type of data required'.