SAP TFC_SCREEN200 Function Module for









TFC_SCREEN200 is a standard tfc screen200 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for tfc screen200 FM, simply by entering the name TFC_SCREEN200 into the relevant SAP transaction such as SE37 or SE38.

Function Group: TFC_DYNP_HANDLING
Program Name: SAPLTFC_DYNP_HANDLING
Main Program: SAPLTFC_DYNP_HANDLING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TFC_SCREEN200 pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TFC_SCREEN200'"
EXPORTING
IFC_TASK_SELECT = "Node Element

CHANGING
CT_RT_PARAMS = "Table of Parameter Values of a Remote Task

EXCEPTIONS
ERROR_OCCURED = 1
.



IMPORTING Parameters details for TFC_SCREEN200

IFC_TASK_SELECT - Node Element

Data type: TFC_TASK_SELECT
Optional: No
Call by Reference: Yes

CHANGING Parameters details for TFC_SCREEN200

CT_RT_PARAMS - Table of Parameter Values of a Remote Task

Data type: TFC_T_PARAM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TFC_SCREEN200 Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_ct_rt_params  TYPE TFC_T_PARAM, "   
lv_error_occured  TYPE TFC_T_PARAM, "   
lv_ifc_task_select  TYPE TFC_TASK_SELECT. "   

  CALL FUNCTION 'TFC_SCREEN200'  "
    EXPORTING
         IFC_TASK_SELECT = lv_ifc_task_select
    CHANGING
         CT_RT_PARAMS = lv_ct_rt_params
    EXCEPTIONS
        ERROR_OCCURED = 1
. " TFC_SCREEN200




ABAP code using 7.40 inline data declarations to call FM TFC_SCREEN200

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!