STC_TM_SESSION_EXPORT_DEL SAP Function module - Delete exported Task List Run

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

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

Pattern for FM STC_TM_SESSION_EXPORT_DEL - STC TM SESSION EXPORT DEL

CALL FUNCTION 'STC_TM_SESSION_EXPORT_DEL' "Delete exported Task List Run
  EXPORTING
    i_session_id =              " stc_session_id  TC Task List Run
*   i_location =                " stc_expimp_location  Location for Export/Import Root Directory
*   is_caller_info =            " stc_ext_caller_info  External Caller Information
  IMPORTING
    e_deleted =                 " sap_bool      'X' = Task List Run is deleted or does not exist
* TABLES
*   et_return =                 " bapirettab    Table with BAPI Return Information
    .  "  STC_TM_SESSION_EXPORT_DEL

ABAP code example for Function Module STC_TM_SESSION_EXPORT_DEL

The ABAP code below is a full code listing to execute function module STC_TM_SESSION_EXPORT_DEL 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_e_deleted  
 
 TYPE SAP_BOOL
,
it_et_return  
 
 TYPE STANDARD TABLE OF BAPIRETTAB,"TABLES PARAM
wa_et_return
 
 LIKE LINE OF it_et_return
.


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

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

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

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
.

CALL FUNCTION 'STC_TM_SESSION_EXPORT_DEL'
  EXPORTING
    i_session_id =               ld_i_session_id
*   i_location =                 ld_i_location
*   is_caller_info =             ld_is_caller_info
  IMPORTING
    e_deleted =                  ld_e_deleted
* TABLES
*   et_return =                  it_et_return
    .  "  STC_TM_SESSION_EXPORT_DEL

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_e_deleted
 
 TYPE SAP_BOOL ,
ld_i_session_id
 
 TYPE STC_SESSION_ID ,
it_et_return
 
 TYPE STANDARD TABLE OF BAPIRETTAB ,
wa_et_return
 
 LIKE LINE OF it_et_return,
ld_i_location
 
 TYPE STC_EXPIMP_LOCATION ,
ld_is_caller_info
 
 TYPE STC_EXT_CALLER_INFO .


ld_i_session_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
ld_i_location = 'Check type of data required'.
ld_is_caller_info = 'Check type of data required'.