TFC_CREATE_TASKLIST SAP Function module

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

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

Pattern for FM TFC_CREATE_TASKLIST - TFC CREATE TASKLIST

CALL FUNCTION 'TFC_CREATE_TASKLIST' "
  EXPORTING
    id_profile =                " tfc_profile
*   id_key_date =               " tfc_stidat
*   id_description =            " tfc_profile_text
*   id_closing_type =           " tfc_closing_type
*   id_fiscal_year =            " gjahr
*   id_posting_period =         " poper
*   id_status =                 " tfc_ready
*   id_responsible =            " tfc_tasklist_res
*   id_authorization_group =    " tfc_authgrp
*   id_schedule_task =          " boole_d
    .  "  TFC_CREATE_TASKLIST

ABAP code example for Function Module TFC_CREATE_TASKLIST

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'TFC_CREATE_TASKLIST'
  EXPORTING
    id_profile =                 ld_id_profile
*   id_key_date =                ld_id_key_date
*   id_description =             ld_id_description
*   id_closing_type =            ld_id_closing_type
*   id_fiscal_year =             ld_id_fiscal_year
*   id_posting_period =          ld_id_posting_period
*   id_status =                  ld_id_status
*   id_responsible =             ld_id_responsible
*   id_authorization_group =     ld_id_authorization_group
*   id_schedule_task =           ld_id_schedule_task
    .  "  TFC_CREATE_TASKLIST

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_id_profile
 
 TYPE TFC_PROFILE ,
ld_id_key_date
 
 TYPE TFC_STIDAT ,
ld_id_description
 
 TYPE TFC_PROFILE_TEXT ,
ld_id_closing_type
 
 TYPE TFC_CLOSING_TYPE ,
ld_id_fiscal_year
 
 TYPE GJAHR ,
ld_id_posting_period
 
 TYPE POPER ,
ld_id_status
 
 TYPE TFC_READY ,
ld_id_responsible
 
 TYPE TFC_TASKLIST_RES ,
ld_id_authorization_group
 
 TYPE TFC_AUTHGRP ,
ld_id_schedule_task
 
 TYPE BOOLE_D .


ld_id_profile = 'Check type of data required'.
ld_id_key_date = 'Check type of data required'.
ld_id_description = 'Check type of data required'.
ld_id_closing_type = 'Check type of data required'.
ld_id_fiscal_year = 'Check type of data required'.
ld_id_posting_period = 'Check type of data required'.
ld_id_status = 'Check type of data required'.
ld_id_responsible = 'Check type of data required'.
ld_id_authorization_group = 'Check type of data required'.
ld_id_schedule_task = 'Check type of data required'.