SAP TTS_SET_SUBSCREEN_DATA_3060 Function Module for Set data for subscreen Changes
TTS_SET_SUBSCREEN_DATA_3060 is a standard tts set subscreen data 3060 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set data for subscreen Changes 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 tts set subscreen data 3060 FM, simply by entering the name TTS_SET_SUBSCREEN_DATA_3060 into the relevant SAP transaction such as SE37 or SE38.
Function Group: TTS_WT
Program Name: SAPLTTS_WT
Main Program: SAPLTTS_WT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TTS_SET_SUBSCREEN_DATA_3060 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 'TTS_SET_SUBSCREEN_DATA_3060'"Set data for subscreen Changes.
EXPORTING
I_OBJNR = "Object number
IS_WAPI = "WCM: I/O Application
IMPORTING Parameters details for TTS_SET_SUBSCREEN_DATA_3060
I_OBJNR - Object number
Data type: J_OBJNROptional: No
Call by Reference: Yes
IS_WAPI - WCM: I/O Application
Data type: WCSWAPIOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TTS_SET_SUBSCREEN_DATA_3060 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_i_objnr | TYPE J_OBJNR, " | |||
| lv_is_wapi | TYPE WCSWAPI. " |
|   CALL FUNCTION 'TTS_SET_SUBSCREEN_DATA_3060' "Set data for subscreen Changes |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| IS_WAPI | = lv_is_wapi | |
| . " TTS_SET_SUBSCREEN_DATA_3060 | ||
ABAP code using 7.40 inline data declarations to call FM TTS_SET_SUBSCREEN_DATA_3060
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