SPI_AGENT_TRFC_END_VB SAP Function module

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

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

Pattern for FM SPI_AGENT_TRFC_END_VB - SPI AGENT TRFC END VB

CALL FUNCTION 'SPI_AGENT_TRFC_END_VB' "
* EXPORTING
*   is_status =                 " arfcsstate    Obsolete
*   ip_qin_name =               " trfcqnam      Obsolete
*   ip_qout_name =              " trfcqnam      Obsolete
*   ip_qflag =                  " c             Obsolete
*   ip_qstate =                 " arfcsstate-arfcstate  Status of an ARFC call (RECORDED,CPICERR,MAILED,READ..)
*   ip_message =                " trfcqview-errmess  Error Text
* TABLES
*   it_status =                 " arfcsstate    Description of ARFC Call Status (Send)
    .  "  SPI_AGENT_TRFC_END_VB

ABAP code example for Function Module SPI_AGENT_TRFC_END_VB

The ABAP code below is a full code listing to execute function module SPI_AGENT_TRFC_END_VB 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:
it_it_status  
 
 TYPE STANDARD TABLE OF ARFCSSTATE,"TABLES PARAM
wa_it_status
 
 LIKE LINE OF it_it_status
.


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

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

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

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

SELECT single ARFCSTATE 
  FROM ARFCSSTATE 
  INTO @DATA(ld_ip_qstate).



DATA(ld_ip_message) = some text here
 

"populate fields of struture and append to itab
append wa_it_status to it_it_status.
.

CALL FUNCTION 'SPI_AGENT_TRFC_END_VB'
* EXPORTING
*   is_status =                  ld_is_status
*   ip_qin_name =                ld_ip_qin_name
*   ip_qout_name =               ld_ip_qout_name
*   ip_qflag =                   ld_ip_qflag
*   ip_qstate =                  ld_ip_qstate
*   ip_message =                 ld_ip_message
* TABLES
*   it_status =                  it_it_status
    .  "  SPI_AGENT_TRFC_END_VB

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_is_status
 
 TYPE ARFCSSTATE ,
it_it_status
 
 TYPE STANDARD TABLE OF ARFCSSTATE ,
wa_it_status
 
 LIKE LINE OF it_it_status,
ld_ip_qin_name
 
 TYPE TRFCQNAM ,
ld_ip_qout_name
 
 TYPE TRFCQNAM ,
ld_ip_qflag
 
 TYPE C ,
ld_ip_qstate
 
 TYPE ARFCSSTATE-ARFCSTATE ,
ld_ip_message
 
 TYPE TRFCQVIEW-ERRMESS .


ld_is_status = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_status to it_it_status.
ld_ip_qin_name = 'Check type of data required'.
ld_ip_qout_name = 'Check type of data required'.
ld_ip_qflag = 'Check type of data required'.

SELECT single ARFCSTATE 
  FROM ARFCSSTATE 
  INTO ld_ip_qstate.


ld_ip_message = some text here