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

Function FITP_CREATE_ITEM_PROPOSAL 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_CREATE_ITEM_PROPOSAL'".
EXPORTING
CATEGORY = "
* FLIGHT_DEP_DEFAULT = "
USERG = "Office Find
* SW_PORTAL = "Single-Character Indicator
IMPORTING
LOCATION_BEGIN = "
IATA_LOCATION_BEGIN = "
DATE_BEGIN = "
TIME_BEGIN = "
LOCATION_END = "
IATA_LOCATION_END = "
DATE_END = "
TIME_END = "
TABLES
T_ITEM = "
T_FLIGHT = "
* T_TRAIN = "
T_USER_CATEGORIES = "
IMPORTING Parameters details for FITP_CREATE_ITEM_PROPOSAL
CATEGORY -
Data type: FTPT_ITEM-CATEGORYOptional: No
Call by Reference: Yes
FLIGHT_DEP_DEFAULT -
Data type: P0471-DEFAPOptional: Yes
Call by Reference: Yes
USERG - Office Find
Data type: OFFICE_FINDOptional: No
Call by Reference: Yes
SW_PORTAL - Single-Character Indicator
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FITP_CREATE_ITEM_PROPOSAL
LOCATION_BEGIN -
Data type: TA21L1-NAMEOptional: No
Call by Reference: Yes
IATA_LOCATION_BEGIN -
Data type: TA21L1-LOCIDOptional: No
Call by Reference: Yes
DATE_BEGIN -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
TIME_BEGIN -
Data type: SY-UZEITOptional: No
Call by Reference: Yes
LOCATION_END -
Data type: TA21L1-NAMEOptional: No
Call by Reference: Yes
IATA_LOCATION_END -
Data type: TA21L1-LOCIDOptional: No
Call by Reference: Yes
DATE_END -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
TIME_END -
Data type: SY-UZEITOptional: No
Call by Reference: Yes
TABLES Parameters details for FITP_CREATE_ITEM_PROPOSAL
T_ITEM -
Data type: FTPT_ITEMOptional: No
Call by Reference: No ( called with pass by value option)
T_FLIGHT -
Data type: FTPT_FLIGHTOptional: No
Call by Reference: No ( called with pass by value option)
T_TRAIN -
Data type: FTPT_TRAINOptional: Yes
Call by Reference: Yes
T_USER_CATEGORIES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FITP_CREATE_ITEM_PROPOSAL 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: | ||||
| lt_t_item | TYPE STANDARD TABLE OF FTPT_ITEM, " | |||
| lv_category | TYPE FTPT_ITEM-CATEGORY, " | |||
| lv_location_begin | TYPE TA21L1-NAME, " | |||
| lt_t_flight | TYPE STANDARD TABLE OF FTPT_FLIGHT, " | |||
| lv_flight_dep_default | TYPE P0471-DEFAP, " | |||
| lv_iata_location_begin | TYPE TA21L1-LOCID, " | |||
| lv_userg | TYPE OFFICE_FIND, " | |||
| lt_t_train | TYPE STANDARD TABLE OF FTPT_TRAIN, " | |||
| lv_date_begin | TYPE SY-DATUM, " | |||
| lv_sw_portal | TYPE CHAR1, " | |||
| lv_time_begin | TYPE SY-UZEIT, " | |||
| lt_t_user_categories | TYPE STANDARD TABLE OF SY, " | |||
| lv_location_end | TYPE TA21L1-NAME, " | |||
| lv_iata_location_end | TYPE TA21L1-LOCID, " | |||
| lv_date_end | TYPE SY-DATUM, " | |||
| lv_time_end | TYPE SY-UZEIT. " |
|   CALL FUNCTION 'FITP_CREATE_ITEM_PROPOSAL' " |
| EXPORTING | ||
| CATEGORY | = lv_category | |
| FLIGHT_DEP_DEFAULT | = lv_flight_dep_default | |
| USERG | = lv_userg | |
| SW_PORTAL | = lv_sw_portal | |
| IMPORTING | ||
| LOCATION_BEGIN | = lv_location_begin | |
| IATA_LOCATION_BEGIN | = lv_iata_location_begin | |
| DATE_BEGIN | = lv_date_begin | |
| TIME_BEGIN | = lv_time_begin | |
| LOCATION_END | = lv_location_end | |
| IATA_LOCATION_END | = lv_iata_location_end | |
| DATE_END | = lv_date_end | |
| TIME_END | = lv_time_end | |
| TABLES | ||
| T_ITEM | = lt_t_item | |
| T_FLIGHT | = lt_t_flight | |
| T_TRAIN | = lt_t_train | |
| T_USER_CATEGORIES | = lt_t_user_categories | |
| . " FITP_CREATE_ITEM_PROPOSAL | ||
ABAP code using 7.40 inline data declarations to call FM FITP_CREATE_ITEM_PROPOSAL
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 CATEGORY FROM FTPT_ITEM INTO @DATA(ld_category). | ||||
| "SELECT single NAME FROM TA21L1 INTO @DATA(ld_location_begin). | ||||
| "SELECT single DEFAP FROM P0471 INTO @DATA(ld_flight_dep_default). | ||||
| "SELECT single LOCID FROM TA21L1 INTO @DATA(ld_iata_location_begin). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date_begin). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_time_begin). | ||||
| "SELECT single NAME FROM TA21L1 INTO @DATA(ld_location_end). | ||||
| "SELECT single LOCID FROM TA21L1 INTO @DATA(ld_iata_location_end). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date_end). | ||||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_time_end). | ||||
Search for further information about these or an SAP related objects