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

Function FITP_READ_PLAN_REQUEST_DATA 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_READ_PLAN_REQUEST_DATA'".
EXPORTING
PERNR = "Personnel Number
REINR = "Trip Number
HDVRS = "
PLANNR = "Task List Number
* ONLY_NEWEST = "
IMPORTING
NUMBER_OF_VARIANTS = "Number of Variants
WA_REQ_HEAD = "Framework Data of Travel Request
WA_PLAN = "General Plan Data
WA_HEAD = "General Trip Data
WA_PERIO = "Period Data of a Trip
TABLES
T_VARIANT = "
T_HOTEL = "
T_HOTEL_PREF = "Hotel service preferences of a travel plan
T_CAR = "Travel Request Item - Car Rental Service
T_CAR_PREF = "Rental car service preferences of a travel plan
T_TRAIN = "Travel Request Item - Train Service
T_TRAIN_PREF = "Train service preferences of a travel plan
* T_OTHER = "Travel Reservation Request Item - Other Service
T_PNR = "Elements of passenger name records of travel plan variant
T_PNR_NAME = "Name element of PNR
T_PNR_OSI = "Other PNR service information
T_ITEM = "
T_PNR_PHONE = "PNR telephone references
T_PNR_ADDRESS = "PNR delivery / billing addresses
T_PNR_REMARKS = "PNR remarks
T_PNR_SSR = "Special PNR service requests
T_TM_MEMO = "Memo table for Travel Management
T_INFO = "Info texts for travel plan variants
* T_SYNC_DATA = "Data Synchronization: SAP - External System
T_REQ_HEAD = "Framework Data of Travel Request
T_REQUEST = "Travel Plan Requests
T_REQ_ADVANCE = "Travel Request Advance
T_FARE_COMP = "Rate components
T_REQ_ACCOUNT = "Travel Request Cost Assignment
T_REQ_REASON = "Reason for Travel Request
* T_USER = "Field String/Table for USER Screen
T_FLIGHT = "
T_FLIGHT_LEG = "Leg of flight
T_FLIGHT_PREF = "Flight service preferences of a travel plan
T_FLIGHT_FARE = "Assignment table: flights <-> rate components
T_FLIGHT_TST = "Ticket information
* T_FARE_NOTE = "Rate Rules
EXCEPTIONS
NO_VARIANT_FOUND = 1
IMPORTING Parameters details for FITP_READ_PLAN_REQUEST_DATA
PERNR - Personnel Number
Data type: PTRV_HEAD-PERNROptional: No
Call by Reference: No ( called with pass by value option)
REINR - Trip Number
Data type: PTRV_HEAD-REINROptional: No
Call by Reference: No ( called with pass by value option)
HDVRS -
Data type: PTRV_HEAD-HDVRSOptional: No
Call by Reference: No ( called with pass by value option)
PLANNR - Task List Number
Data type: FTPT_PLAN-PLANNROptional: No
Call by Reference: No ( called with pass by value option)
ONLY_NEWEST -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FITP_READ_PLAN_REQUEST_DATA
NUMBER_OF_VARIANTS - Number of Variants
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
WA_REQ_HEAD - Framework Data of Travel Request
Data type: FTPT_REQ_HEADOptional: No
Call by Reference: Yes
WA_PLAN - General Plan Data
Data type: FTPT_PLANOptional: No
Call by Reference: Yes
WA_HEAD - General Trip Data
Data type: PTRV_HEADOptional: No
Call by Reference: Yes
WA_PERIO - Period Data of a Trip
Data type: PTRV_PERIOOptional: No
Call by Reference: Yes
TABLES Parameters details for FITP_READ_PLAN_REQUEST_DATA
T_VARIANT -
Data type: FTPT_VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
T_HOTEL -
Data type: FTPT_HOTELOptional: No
Call by Reference: No ( called with pass by value option)
T_HOTEL_PREF - Hotel service preferences of a travel plan
Data type: FTPT_HOTEL_PREFOptional: No
Call by Reference: Yes
T_CAR - Travel Request Item - Car Rental Service
Data type: FTPT_CAROptional: No
Call by Reference: Yes
T_CAR_PREF - Rental car service preferences of a travel plan
Data type: FTPT_CAR_PREFOptional: No
Call by Reference: Yes
T_TRAIN - Travel Request Item - Train Service
Data type: FTPT_TRAINOptional: No
Call by Reference: Yes
T_TRAIN_PREF - Train service preferences of a travel plan
Data type: FTPT_TRAIN_PREFOptional: No
Call by Reference: Yes
T_OTHER - Travel Reservation Request Item - Other Service
Data type: FTPT_OTHEROptional: Yes
Call by Reference: Yes
T_PNR - Elements of passenger name records of travel plan variant
Data type: FTPT_PNROptional: No
Call by Reference: Yes
T_PNR_NAME - Name element of PNR
Data type: FTPT_PNR_NAMEOptional: No
Call by Reference: Yes
T_PNR_OSI - Other PNR service information
Data type: FTPT_PNR_OSIOptional: No
Call by Reference: Yes
T_ITEM -
Data type: FTPT_ITEMOptional: No
Call by Reference: No ( called with pass by value option)
T_PNR_PHONE - PNR telephone references
Data type: FTPT_PNR_PHONEOptional: No
Call by Reference: Yes
T_PNR_ADDRESS - PNR delivery / billing addresses
Data type: FTPT_PNR_ADDRESSOptional: No
Call by Reference: Yes
T_PNR_REMARKS - PNR remarks
Data type: FTPT_PNR_REMARKSOptional: No
Call by Reference: Yes
T_PNR_SSR - Special PNR service requests
Data type: FTPT_PNR_SSROptional: No
Call by Reference: Yes
T_TM_MEMO - Memo table for Travel Management
Data type: FTPT_TM_MEMOOptional: No
Call by Reference: Yes
T_INFO - Info texts for travel plan variants
Data type: FTPT_VAR_INFOOptional: No
Call by Reference: Yes
T_SYNC_DATA - Data Synchronization: SAP - External System
Data type: FTPT_SYNC_DATAOptional: Yes
Call by Reference: Yes
T_REQ_HEAD - Framework Data of Travel Request
Data type: FTPT_REQ_HEADOptional: No
Call by Reference: Yes
T_REQUEST - Travel Plan Requests
Data type: FTPT_REQUESTOptional: No
Call by Reference: Yes
T_REQ_ADVANCE - Travel Request Advance
Data type: FTPT_REQ_ADVANCEOptional: No
Call by Reference: Yes
T_FARE_COMP - Rate components
Data type: FTPT_FARE_COMPOptional: No
Call by Reference: Yes
T_REQ_ACCOUNT - Travel Request Cost Assignment
Data type: FTPT_REQ_ACCOUNTOptional: No
Call by Reference: Yes
T_REQ_REASON - Reason for Travel Request
Data type: FTPT_REQ_REASONOptional: No
Call by Reference: Yes
T_USER - Field String/Table for USER Screen
Data type: PTK99Optional: Yes
Call by Reference: Yes
T_FLIGHT -
Data type: FTPT_FLIGHTOptional: No
Call by Reference: No ( called with pass by value option)
T_FLIGHT_LEG - Leg of flight
Data type: FTPT_FLIGHT_LEGOptional: No
Call by Reference: Yes
T_FLIGHT_PREF - Flight service preferences of a travel plan
Data type: FTPT_FLIGHT_PREFOptional: No
Call by Reference: Yes
T_FLIGHT_FARE - Assignment table: flights <-> rate components
Data type: FTPT_FLIGHT_FCMPOptional: No
Call by Reference: Yes
T_FLIGHT_TST - Ticket information
Data type: FTPT_FLIGHT_TSTKOptional: No
Call by Reference: Yes
T_FARE_NOTE - Rate Rules
Data type: FTPT_FARE_NOTEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_VARIANT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FITP_READ_PLAN_REQUEST_DATA 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_pernr | TYPE PTRV_HEAD-PERNR, " | |||
| lt_t_variant | TYPE STANDARD TABLE OF FTPT_VARIANT, " | |||
| lv_no_variant_found | TYPE FTPT_VARIANT, " | |||
| lv_number_of_variants | TYPE I, " | |||
| lt_t_hotel | TYPE STANDARD TABLE OF FTPT_HOTEL, " | |||
| lt_t_hotel_pref | TYPE STANDARD TABLE OF FTPT_HOTEL_PREF, " | |||
| lt_t_car | TYPE STANDARD TABLE OF FTPT_CAR, " | |||
| lt_t_car_pref | TYPE STANDARD TABLE OF FTPT_CAR_PREF, " | |||
| lt_t_train | TYPE STANDARD TABLE OF FTPT_TRAIN, " | |||
| lt_t_train_pref | TYPE STANDARD TABLE OF FTPT_TRAIN_PREF, " | |||
| lt_t_other | TYPE STANDARD TABLE OF FTPT_OTHER, " | |||
| lt_t_pnr | TYPE STANDARD TABLE OF FTPT_PNR, " | |||
| lt_t_pnr_name | TYPE STANDARD TABLE OF FTPT_PNR_NAME, " | |||
| lt_t_pnr_osi | TYPE STANDARD TABLE OF FTPT_PNR_OSI, " | |||
| lv_reinr | TYPE PTRV_HEAD-REINR, " | |||
| lt_t_item | TYPE STANDARD TABLE OF FTPT_ITEM, " | |||
| lv_wa_req_head | TYPE FTPT_REQ_HEAD, " | |||
| lt_t_pnr_phone | TYPE STANDARD TABLE OF FTPT_PNR_PHONE, " | |||
| lt_t_pnr_address | TYPE STANDARD TABLE OF FTPT_PNR_ADDRESS, " | |||
| lt_t_pnr_remarks | TYPE STANDARD TABLE OF FTPT_PNR_REMARKS, " | |||
| lt_t_pnr_ssr | TYPE STANDARD TABLE OF FTPT_PNR_SSR, " | |||
| lt_t_tm_memo | TYPE STANDARD TABLE OF FTPT_TM_MEMO, " | |||
| lt_t_info | TYPE STANDARD TABLE OF FTPT_VAR_INFO, " | |||
| lt_t_sync_data | TYPE STANDARD TABLE OF FTPT_SYNC_DATA, " | |||
| lt_t_req_head | TYPE STANDARD TABLE OF FTPT_REQ_HEAD, " | |||
| lt_t_request | TYPE STANDARD TABLE OF FTPT_REQUEST, " | |||
| lt_t_req_advance | TYPE STANDARD TABLE OF FTPT_REQ_ADVANCE, " | |||
| lv_hdvrs | TYPE PTRV_HEAD-HDVRS, " | |||
| lv_wa_plan | TYPE FTPT_PLAN, " | |||
| lt_t_fare_comp | TYPE STANDARD TABLE OF FTPT_FARE_COMP, " | |||
| lt_t_req_account | TYPE STANDARD TABLE OF FTPT_REQ_ACCOUNT, " | |||
| lt_t_req_reason | TYPE STANDARD TABLE OF FTPT_REQ_REASON, " | |||
| lt_t_user | TYPE STANDARD TABLE OF PTK99, " | |||
| lv_plannr | TYPE FTPT_PLAN-PLANNR, " | |||
| lv_wa_head | TYPE PTRV_HEAD, " | |||
| lt_t_flight | TYPE STANDARD TABLE OF FTPT_FLIGHT, " | |||
| lv_wa_perio | TYPE PTRV_PERIO, " | |||
| lv_only_newest | TYPE C, " | |||
| lt_t_flight_leg | TYPE STANDARD TABLE OF FTPT_FLIGHT_LEG, " | |||
| lt_t_flight_pref | TYPE STANDARD TABLE OF FTPT_FLIGHT_PREF, " | |||
| lt_t_flight_fare | TYPE STANDARD TABLE OF FTPT_FLIGHT_FCMP, " | |||
| lt_t_flight_tst | TYPE STANDARD TABLE OF FTPT_FLIGHT_TSTK, " | |||
| lt_t_fare_note | TYPE STANDARD TABLE OF FTPT_FARE_NOTE. " |
|   CALL FUNCTION 'FITP_READ_PLAN_REQUEST_DATA' " |
| EXPORTING | ||
| PERNR | = lv_pernr | |
| REINR | = lv_reinr | |
| HDVRS | = lv_hdvrs | |
| PLANNR | = lv_plannr | |
| ONLY_NEWEST | = lv_only_newest | |
| IMPORTING | ||
| NUMBER_OF_VARIANTS | = lv_number_of_variants | |
| WA_REQ_HEAD | = lv_wa_req_head | |
| WA_PLAN | = lv_wa_plan | |
| WA_HEAD | = lv_wa_head | |
| WA_PERIO | = lv_wa_perio | |
| TABLES | ||
| T_VARIANT | = lt_t_variant | |
| T_HOTEL | = lt_t_hotel | |
| T_HOTEL_PREF | = lt_t_hotel_pref | |
| T_CAR | = lt_t_car | |
| T_CAR_PREF | = lt_t_car_pref | |
| T_TRAIN | = lt_t_train | |
| T_TRAIN_PREF | = lt_t_train_pref | |
| T_OTHER | = lt_t_other | |
| T_PNR | = lt_t_pnr | |
| T_PNR_NAME | = lt_t_pnr_name | |
| T_PNR_OSI | = lt_t_pnr_osi | |
| T_ITEM | = lt_t_item | |
| T_PNR_PHONE | = lt_t_pnr_phone | |
| T_PNR_ADDRESS | = lt_t_pnr_address | |
| T_PNR_REMARKS | = lt_t_pnr_remarks | |
| T_PNR_SSR | = lt_t_pnr_ssr | |
| T_TM_MEMO | = lt_t_tm_memo | |
| T_INFO | = lt_t_info | |
| T_SYNC_DATA | = lt_t_sync_data | |
| T_REQ_HEAD | = lt_t_req_head | |
| T_REQUEST | = lt_t_request | |
| T_REQ_ADVANCE | = lt_t_req_advance | |
| T_FARE_COMP | = lt_t_fare_comp | |
| T_REQ_ACCOUNT | = lt_t_req_account | |
| T_REQ_REASON | = lt_t_req_reason | |
| T_USER | = lt_t_user | |
| T_FLIGHT | = lt_t_flight | |
| T_FLIGHT_LEG | = lt_t_flight_leg | |
| T_FLIGHT_PREF | = lt_t_flight_pref | |
| T_FLIGHT_FARE | = lt_t_flight_fare | |
| T_FLIGHT_TST | = lt_t_flight_tst | |
| T_FARE_NOTE | = lt_t_fare_note | |
| EXCEPTIONS | ||
| NO_VARIANT_FOUND = 1 | ||
| . " FITP_READ_PLAN_REQUEST_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FITP_READ_PLAN_REQUEST_DATA
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 PERNR FROM PTRV_HEAD INTO @DATA(ld_pernr). | ||||
| "SELECT single REINR FROM PTRV_HEAD INTO @DATA(ld_reinr). | ||||
| "SELECT single HDVRS FROM PTRV_HEAD INTO @DATA(ld_hdvrs). | ||||
| "SELECT single PLANNR FROM FTPT_PLAN INTO @DATA(ld_plannr). | ||||
Search for further information about these or an SAP related objects