SAP FITP_QUICKTRIP_SET Function Module for
FITP_QUICKTRIP_SET is a standard fitp quicktrip set 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 fitp quicktrip set FM, simply by entering the name FITP_QUICKTRIP_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_QUICKTRIP
Program Name: SAPLFITP_QUICKTRIP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FITP_QUICKTRIP_SET 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 'FITP_QUICKTRIP_SET'".
EXPORTING
IWA_VARIANT = "
IPROFILE_NAME = "
IACTIVITY_TYPE = "
TABLES
IO_T_ITEM = "
IO_T_QT_ALTERN = "
IO_T_QT_BPROFILE = "
IO_T_FLIGHT = "
IO_T_CAR = "
IO_T_HOTEL = "
IO_T_QT_QTRIP = "
IO_T_QT_FLIGHT = "
IO_T_QT_HOTEL = "
IO_T_QT_CAR = "
IO_T_QT_ITEM = "
EXCEPTIONS
QT_SET = 1 QT_CANCEL = 2 QT_ABORT = 3
IMPORTING Parameters details for FITP_QUICKTRIP_SET
IWA_VARIANT -
Data type: FTPT_VARIANTOptional: No
Call by Reference: Yes
IPROFILE_NAME -
Data type: TA20P-PROFILEOptional: No
Call by Reference: Yes
IACTIVITY_TYPE -
Data type: FTPT_PLAN-ACTIVITY_TYPEOptional: No
Call by Reference: Yes
TABLES Parameters details for FITP_QUICKTRIP_SET
IO_T_ITEM -
Data type: FTPT_ITEMOptional: No
Call by Reference: Yes
IO_T_QT_ALTERN -
Data type: FTPT_QT_ALTERNOptional: No
Call by Reference: Yes
IO_T_QT_BPROFILE -
Data type: FTPT_QT_BPROFILEOptional: No
Call by Reference: Yes
IO_T_FLIGHT -
Data type: FTPT_FLIGHTOptional: No
Call by Reference: Yes
IO_T_CAR -
Data type: FTPT_CAROptional: No
Call by Reference: Yes
IO_T_HOTEL -
Data type: FTPT_HOTELOptional: No
Call by Reference: Yes
IO_T_QT_QTRIP -
Data type: FTPT_QT_QTRIPOptional: No
Call by Reference: Yes
IO_T_QT_FLIGHT -
Data type: FTPT_QT_FLIGHTOptional: No
Call by Reference: Yes
IO_T_QT_HOTEL -
Data type: FTPT_QT_HOTELOptional: No
Call by Reference: Yes
IO_T_QT_CAR -
Data type: FTPT_QT_CAROptional: No
Call by Reference: Yes
IO_T_QT_ITEM -
Data type: FTPT_QT_ITEMOptional: No
Call by Reference: Yes
EXCEPTIONS details
QT_SET -
Data type:Optional: No
Call by Reference: Yes
QT_CANCEL -
Data type:Optional: No
Call by Reference: Yes
QT_ABORT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FITP_QUICKTRIP_SET 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_qt_set | TYPE STRING, " | |||
| lt_io_t_item | TYPE STANDARD TABLE OF FTPT_ITEM, " | |||
| lv_iwa_variant | TYPE FTPT_VARIANT, " | |||
| lt_io_t_qt_altern | TYPE STANDARD TABLE OF FTPT_QT_ALTERN, " | |||
| lt_io_t_qt_bprofile | TYPE STANDARD TABLE OF FTPT_QT_BPROFILE, " | |||
| lv_qt_cancel | TYPE FTPT_QT_BPROFILE, " | |||
| lt_io_t_flight | TYPE STANDARD TABLE OF FTPT_FLIGHT, " | |||
| lv_iprofile_name | TYPE TA20P-PROFILE, " | |||
| lt_io_t_car | TYPE STANDARD TABLE OF FTPT_CAR, " | |||
| lv_qt_abort | TYPE FTPT_CAR, " | |||
| lv_iactivity_type | TYPE FTPT_PLAN-ACTIVITY_TYPE, " | |||
| lt_io_t_hotel | TYPE STANDARD TABLE OF FTPT_HOTEL, " | |||
| lt_io_t_qt_qtrip | TYPE STANDARD TABLE OF FTPT_QT_QTRIP, " | |||
| lt_io_t_qt_flight | TYPE STANDARD TABLE OF FTPT_QT_FLIGHT, " | |||
| lt_io_t_qt_hotel | TYPE STANDARD TABLE OF FTPT_QT_HOTEL, " | |||
| lt_io_t_qt_car | TYPE STANDARD TABLE OF FTPT_QT_CAR, " | |||
| lt_io_t_qt_item | TYPE STANDARD TABLE OF FTPT_QT_ITEM. " |
|   CALL FUNCTION 'FITP_QUICKTRIP_SET' " |
| EXPORTING | ||
| IWA_VARIANT | = lv_iwa_variant | |
| IPROFILE_NAME | = lv_iprofile_name | |
| IACTIVITY_TYPE | = lv_iactivity_type | |
| TABLES | ||
| IO_T_ITEM | = lt_io_t_item | |
| IO_T_QT_ALTERN | = lt_io_t_qt_altern | |
| IO_T_QT_BPROFILE | = lt_io_t_qt_bprofile | |
| IO_T_FLIGHT | = lt_io_t_flight | |
| IO_T_CAR | = lt_io_t_car | |
| IO_T_HOTEL | = lt_io_t_hotel | |
| IO_T_QT_QTRIP | = lt_io_t_qt_qtrip | |
| IO_T_QT_FLIGHT | = lt_io_t_qt_flight | |
| IO_T_QT_HOTEL | = lt_io_t_qt_hotel | |
| IO_T_QT_CAR | = lt_io_t_qt_car | |
| IO_T_QT_ITEM | = lt_io_t_qt_item | |
| EXCEPTIONS | ||
| QT_SET = 1 | ||
| QT_CANCEL = 2 | ||
| QT_ABORT = 3 | ||
| . " FITP_QUICKTRIP_SET | ||
ABAP code using 7.40 inline data declarations to call FM FITP_QUICKTRIP_SET
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.| "SELECT single PROFILE FROM TA20P INTO @DATA(ld_iprofile_name). | ||||
| "SELECT single ACTIVITY_TYPE FROM FTPT_PLAN INTO @DATA(ld_iactivity_type). | ||||
Search for further information about these or an SAP related objects