SAP FCC_SCREEN200 Function Module for Screen 200
FCC_SCREEN200 is a standard fcc screen200 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Screen 200 processing and below is the pattern details for this FM, 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 fcc screen200 FM, simply by entering the name FCC_SCREEN200 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCC_DYNPRO_HANDLING
Program Name: SAPLFCC_DYNPRO_HANDLING
Main Program: SAPLFCC_DYNPRO_HANDLING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FCC_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 'FCC_SCREEN200'"Screen 200.
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 FCC_SCREEN200
IFC_TASK_SELECT - Node Element
Data type: FCC_TASK_SELECTOptional: No
Call by Reference: Yes
CHANGING Parameters details for FCC_SCREEN200
CT_RT_PARAMS - Table of Parameter Values of a Remote Task
Data type: FCC_T_PARAMOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FCC_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 FCC_T_PARAM, " | |||
| lv_error_occured | TYPE FCC_T_PARAM, " | |||
| lv_ifc_task_select | TYPE FCC_TASK_SELECT. " |
|   CALL FUNCTION 'FCC_SCREEN200' "Screen 200 |
| EXPORTING | ||
| IFC_TASK_SELECT | = lv_ifc_task_select | |
| CHANGING | ||
| CT_RT_PARAMS | = lv_ct_rt_params | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " FCC_SCREEN200 | ||
ABAP code using 7.40 inline data declarations to call FM FCC_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