SAP STU4_CCMS_CP_CALL_SCREEN Function Module for DB6: Call Screen via Framework
STU4_CCMS_CP_CALL_SCREEN is a standard stu4 ccms cp call screen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB6: Call Screen via Framework 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 stu4 ccms cp call screen FM, simply by entering the name STU4_CCMS_CP_CALL_SCREEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU4_CCMS_CP
Program Name: SAPLSTU4_CCMS_CP
Main Program: SAPLSTU4_CCMS_CP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STU4_CCMS_CP_CALL_SCREEN 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 'STU4_CCMS_CP_CALL_SCREEN'"DB6: Call Screen via Framework.
EXPORTING
SCREEN = "ABAP program, number of current screen
* X_COORD = "
* Y_COORD = "
IMPORTING Parameters details for STU4_CCMS_CP_CALL_SCREEN
SCREEN - ABAP program, number of current screen
Data type: SYDYNNROptional: No
Call by Reference: Yes
X_COORD -
Data type: IOptional: Yes
Call by Reference: Yes
Y_COORD -
Data type: IOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for STU4_CCMS_CP_CALL_SCREEN 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_screen | TYPE SYDYNNR, " | |||
| lv_x_coord | TYPE I, " | |||
| lv_y_coord | TYPE I. " |
|   CALL FUNCTION 'STU4_CCMS_CP_CALL_SCREEN' "DB6: Call Screen via Framework |
| EXPORTING | ||
| SCREEN | = lv_screen | |
| X_COORD | = lv_x_coord | |
| Y_COORD | = lv_y_coord | |
| . " STU4_CCMS_CP_CALL_SCREEN | ||
ABAP code using 7.40 inline data declarations to call FM STU4_CCMS_CP_CALL_SCREEN
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