SPI_ALERT_TEST_PROCESS_STEP SAP Function module

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

Associated Function Group: SPI93
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM SPI_ALERT_TEST_PROCESS_STEP - SPI ALERT TEST PROCESS STEP

CALL FUNCTION 'SPI_ALERT_TEST_PROCESS_STEP' "
  EXPORTING
    i_cnd =                     " spiattval
*   i_wait = 0                  " i
*   it_field_values =           " tspinv
    it_id1 =                    " tspinv
*   it_id2 =                    " tspinv
*   i_error = '00'              " spierrst
*   i_forced_finish =           " spicmpfin
    .  "  SPI_ALERT_TEST_PROCESS_STEP

ABAP code example for Function Module SPI_ALERT_TEST_PROCESS_STEP

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

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

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

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

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

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

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

CALL FUNCTION 'SPI_ALERT_TEST_PROCESS_STEP'
  EXPORTING
    i_cnd =                      ld_i_cnd
*   i_wait =                     ld_i_wait
*   it_field_values =            ld_it_field_values
    it_id1 =                     ld_it_id1
*   it_id2 =                     ld_it_id2
*   i_error =                    ld_i_error
*   i_forced_finish =            ld_i_forced_finish
    .  "  SPI_ALERT_TEST_PROCESS_STEP

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_i_cnd
 
 TYPE SPIATTVAL ,
ld_i_wait
 
 TYPE I ,
ld_it_field_values
 
 TYPE TSPINV ,
ld_it_id1
 
 TYPE TSPINV ,
ld_it_id2
 
 TYPE TSPINV ,
ld_i_error
 
 TYPE SPIERRST ,
ld_i_forced_finish
 
 TYPE SPICMPFIN .


ld_i_cnd = 'Check type of data required'.
ld_i_wait = 'Check type of data required'.
ld_it_field_values = 'Check type of data required'.
ld_it_id1 = 'Check type of data required'.
ld_it_id2 = 'Check type of data required'.
ld_i_error = 'Check type of data required'.
ld_i_forced_finish = 'Check type of data required'.