SRT_TARGET_PROVIDER_ASYNC2 SAP Function module - Second Target Mapping provider (asynchronous processing)

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

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

Pattern for FM SRT_TARGET_PROVIDER_ASYNC2 - SRT TARGET PROVIDER ASYNC2

CALL FUNCTION 'SRT_TARGET_PROVIDER_ASYNC2' "Second Target Mapping provider (asynchronous processing)
  EXPORTING
    iv_action =                 " string
    iv_passport_id =            " char32        Character field, length 32
    iv_message_id =             " char32        Character field, length 32
    iv_sequence_id =            " char32        Character field, length 32
    iv_running_number =         " sytabix       Index of Internal Tables
    iv_string =                 " string
    .  "  SRT_TARGET_PROVIDER_ASYNC2

ABAP code example for Function Module SRT_TARGET_PROVIDER_ASYNC2

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

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

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

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

DATA(ld_iv_running_number) = '123 '.

DATA(ld_iv_string) = '123 '.
.

CALL FUNCTION 'SRT_TARGET_PROVIDER_ASYNC2'
  EXPORTING
    iv_action =                  ld_iv_action
    iv_passport_id =             ld_iv_passport_id
    iv_message_id =              ld_iv_message_id
    iv_sequence_id =             ld_iv_sequence_id
    iv_running_number =          ld_iv_running_number
    iv_string =                  ld_iv_string
    .  "  SRT_TARGET_PROVIDER_ASYNC2

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_iv_action
 
 TYPE STRING ,
ld_iv_passport_id
 
 TYPE CHAR32 ,
ld_iv_message_id
 
 TYPE CHAR32 ,
ld_iv_sequence_id
 
 TYPE CHAR32 ,
ld_iv_running_number
 
 TYPE SYTABIX ,
ld_iv_string
 
 TYPE STRING .


ld_iv_action = '123 '.
ld_iv_passport_id = '123 '.
ld_iv_message_id = '123 '.
ld_iv_sequence_id = '123 '.
ld_iv_running_number = '123 '.
ld_iv_string = '123 '.