ISU_O_TRIGGER_ACTION SAP Function module - INTERNAL: Subscreen Actions

ISU_O_TRIGGER_ACTION 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_ACTION 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_ACTION - ISU O TRIGGER ACTION

CALL FUNCTION 'ISU_O_TRIGGER_ACTION' "INTERNAL: Subscreen Actions
  EXPORTING
    x_okcode =                  " regen-okcode  OK Code (from IEOKCODE)
*   x_no_close =                " regen-kennzx
*   x_no_message =              " regen-kennzx
*   x_other_anlage =            " etrg-anlage
*   x_other_abrdats =           " etrg-abrdats
*   x_other_abrvorg =           " etrg-abrvorg
*   x_no_update =               " regen-kennzx
* CHANGING
*   xy_obj =                    " isu17_trigger  Object Data
*   txy_obj =                   " isu17_trigger_tab
  EXCEPTIONS
    CANCELLED = 1               "               Action terminated by the user
    OPEN_ERROR = 2              "
    NOT_FOUND = 3               "
    .  "  ISU_O_TRIGGER_ACTION

ABAP code example for Function Module ISU_O_TRIGGER_ACTION

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


DATA(ld_x_okcode) = some text here


DATA(ld_x_no_close) = some text here


DATA(ld_x_no_message) = some text here
 

SELECT single ANLAGE 
  FROM ETRG 
  INTO @DATA(ld_x_other_anlage).

 

SELECT single ABRDATS 
  FROM ETRG 
  INTO @DATA(ld_x_other_abrdats).

 

SELECT single ABRVORG 
  FROM ETRG 
  INTO @DATA(ld_x_other_abrvorg).



DATA(ld_x_no_update) = some text here
.

CALL FUNCTION 'ISU_O_TRIGGER_ACTION'
  EXPORTING
    x_okcode =                   ld_x_okcode
*   x_no_close =                 ld_x_no_close
*   x_no_message =               ld_x_no_message
*   x_other_anlage =             ld_x_other_anlage
*   x_other_abrdats =            ld_x_other_abrdats
*   x_other_abrvorg =            ld_x_other_abrvorg
*   x_no_update =                ld_x_no_update
* CHANGING
*   xy_obj =                     ld_xy_obj
*   txy_obj =                    ld_txy_obj
  EXCEPTIONS
    CANCELLED =                  1
    OPEN_ERROR =                 2
    NOT_FOUND =                  3
    .  "  ISU_O_TRIGGER_ACTION

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_xy_obj
 
 TYPE ISU17_TRIGGER ,
ld_x_okcode
 
 TYPE REGEN-OKCODE ,
ld_txy_obj
 
 TYPE ISU17_TRIGGER_TAB ,
ld_x_no_close
 
 TYPE REGEN-KENNZX ,
ld_x_no_message
 
 TYPE REGEN-KENNZX ,
ld_x_other_anlage
 
 TYPE ETRG-ANLAGE ,
ld_x_other_abrdats
 
 TYPE ETRG-ABRDATS ,
ld_x_other_abrvorg
 
 TYPE ETRG-ABRVORG ,
ld_x_no_update
 
 TYPE REGEN-KENNZX .


ld_xy_obj = 'Check type of data required'.

ld_x_okcode = some text here
ld_txy_obj = 'Check type of data required'.

ld_x_no_close = some text here

ld_x_no_message = some text here

SELECT single ANLAGE 
  FROM ETRG 
  INTO ld_x_other_anlage.


SELECT single ABRDATS 
  FROM ETRG 
  INTO ld_x_other_abrdats.


SELECT single ABRVORG 
  FROM ETRG 
  INTO ld_x_other_abrvorg.


ld_x_no_update = some text here