SAP FTR_UTILS_CALUPL_PROCESS Function Module for Calendar Upload processing function
FTR_UTILS_CALUPL_PROCESS is a standard ftr utils calupl process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calendar Upload processing function 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 ftr utils calupl process FM, simply by entering the name FTR_UTILS_CALUPL_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_TRCUT_UTILS
Program Name: SAPLFTR_TRCUT_UTILS
Main Program: SAPLFTR_TRCUT_UTILS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FTR_UTILS_CALUPL_PROCESS 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 'FTR_UTILS_CALUPL_PROCESS'"Calendar Upload processing function.
EXPORTING
IM_TAB_CAL_DATA = "Table with data from calendar upload file
IM_UPLOAD_FLAG = "General Flag
IM_TEST_RUN = "General Flag
IM_LOG_HANDLE = "Application Log: Log Handle Table
IM_CLIENT_ROLE = "Client control: Role of client (production, test,...)
IMPORTING
EX_TAB_LOG_HANDLE = "Application Log: Log Handle Table
EXCEPTIONS
MULTITASKING_FAILED = 1
IMPORTING Parameters details for FTR_UTILS_CALUPL_PROCESS
IM_TAB_CAL_DATA - Table with data from calendar upload file
Data type: TRCUTY_CAL_DATAOptional: No
Call by Reference: No ( called with pass by value option)
IM_UPLOAD_FLAG - General Flag
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IM_TEST_RUN - General Flag
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IM_LOG_HANDLE - Application Log: Log Handle Table
Data type: BALLOGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
IM_CLIENT_ROLE - Client control: Role of client (production, test,...)
Data type: CCCATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_UTILS_CALUPL_PROCESS
EX_TAB_LOG_HANDLE - Application Log: Log Handle Table
Data type: BAL_T_LOGHOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MULTITASKING_FAILED - Multitasking Failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_UTILS_CALUPL_PROCESS 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_im_tab_cal_data | TYPE TRCUTY_CAL_DATA, " | |||
| lv_ex_tab_log_handle | TYPE BAL_T_LOGH, " | |||
| lv_multitasking_failed | TYPE BAL_T_LOGH, " | |||
| lv_im_upload_flag | TYPE BOOLEAN, " | |||
| lv_im_test_run | TYPE BOOLEAN, " | |||
| lv_im_log_handle | TYPE BALLOGHNDL, " | |||
| lv_im_client_role | TYPE CCCATEGORY. " |
|   CALL FUNCTION 'FTR_UTILS_CALUPL_PROCESS' "Calendar Upload processing function |
| EXPORTING | ||
| IM_TAB_CAL_DATA | = lv_im_tab_cal_data | |
| IM_UPLOAD_FLAG | = lv_im_upload_flag | |
| IM_TEST_RUN | = lv_im_test_run | |
| IM_LOG_HANDLE | = lv_im_log_handle | |
| IM_CLIENT_ROLE | = lv_im_client_role | |
| IMPORTING | ||
| EX_TAB_LOG_HANDLE | = lv_ex_tab_log_handle | |
| EXCEPTIONS | ||
| MULTITASKING_FAILED = 1 | ||
| . " FTR_UTILS_CALUPL_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM FTR_UTILS_CALUPL_PROCESS
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