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

Function FITP_REQUEST_TABLES_READ 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_REQUEST_TABLES_READ'".
EXPORTING
PERNR = "Personnel Number
REINR = "Trip Number
* PLAN_REQUEST = 'P' "
* CHANGE_TO_P = "
IMPORTING
WA_REQ_HEAD = "Framework Data of Travel Request
WA_HEAD = "General Trip Data
WA_PERIO = "Period Data of a Trip
ET_REQ_CAT = "DB: Types of Transport/Accomm. and Est.Costs of Trav.Request
TABLES
* T_REQ_HEAD = "Framework Data of Travel Request
* T_REQUEST = "Travel Plan Requests
* T_REQ_ADVANCE = "Travel Request Advance
* T_REQ_ACCOUNT = "Travel Request Cost Assignment
* T_REQ_REASON = "Reason for Travel Request
* T_USER = "Field String/Table for USER Screen
IMPORTING Parameters details for FITP_REQUEST_TABLES_READ
PERNR - Personnel Number
Data type: PTRV_HEAD-PERNROptional: No
Call by Reference: Yes
REINR - Trip Number
Data type: PTRV_HEAD-REINROptional: No
Call by Reference: Yes
PLAN_REQUEST -
Data type: CHAR1Default: 'P'
Optional: No
Call by Reference: Yes
CHANGE_TO_P -
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FITP_REQUEST_TABLES_READ
WA_REQ_HEAD - Framework Data of Travel Request
Data type: FTPT_REQ_HEADOptional: 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
ET_REQ_CAT - DB: Types of Transport/Accomm. and Est.Costs of Trav.Request
Data type: FTPT_REQ_CAT_TOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FITP_REQUEST_TABLES_READ
T_REQ_HEAD - Framework Data of Travel Request
Data type: FTPT_REQ_HEADOptional: Yes
Call by Reference: Yes
T_REQUEST - Travel Plan Requests
Data type: FTPT_REQUESTOptional: Yes
Call by Reference: Yes
T_REQ_ADVANCE - Travel Request Advance
Data type: FTPT_REQ_ADVANCEOptional: Yes
Call by Reference: Yes
T_REQ_ACCOUNT - Travel Request Cost Assignment
Data type: FTPT_REQ_ACCOUNTOptional: Yes
Call by Reference: Yes
T_REQ_REASON - Reason for Travel Request
Data type: FTPT_REQ_REASONOptional: Yes
Call by Reference: Yes
T_USER - Field String/Table for USER Screen
Data type: PTK99Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FITP_REQUEST_TABLES_READ 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_req_head | TYPE STANDARD TABLE OF FTPT_REQ_HEAD, " | |||
| lv_wa_req_head | TYPE FTPT_REQ_HEAD, " | |||
| lv_reinr | TYPE PTRV_HEAD-REINR, " | |||
| lv_wa_head | TYPE PTRV_HEAD, " | |||
| lt_t_request | TYPE STANDARD TABLE OF FTPT_REQUEST, " | |||
| lv_wa_perio | TYPE PTRV_PERIO, " | |||
| lv_plan_request | TYPE CHAR1, " 'P' | |||
| lt_t_req_advance | TYPE STANDARD TABLE OF FTPT_REQ_ADVANCE, " | |||
| lv_et_req_cat | TYPE FTPT_REQ_CAT_T, " | |||
| lv_change_to_p | TYPE XFELD, " | |||
| 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. " |
|   CALL FUNCTION 'FITP_REQUEST_TABLES_READ' " |
| EXPORTING | ||
| PERNR | = lv_pernr | |
| REINR | = lv_reinr | |
| PLAN_REQUEST | = lv_plan_request | |
| CHANGE_TO_P | = lv_change_to_p | |
| IMPORTING | ||
| WA_REQ_HEAD | = lv_wa_req_head | |
| WA_HEAD | = lv_wa_head | |
| WA_PERIO | = lv_wa_perio | |
| ET_REQ_CAT | = lv_et_req_cat | |
| TABLES | ||
| T_REQ_HEAD | = lt_t_req_head | |
| T_REQUEST | = lt_t_request | |
| T_REQ_ADVANCE | = lt_t_req_advance | |
| T_REQ_ACCOUNT | = lt_t_req_account | |
| T_REQ_REASON | = lt_t_req_reason | |
| T_USER | = lt_t_user | |
| . " FITP_REQUEST_TABLES_READ | ||
ABAP code using 7.40 inline data declarations to call FM FITP_REQUEST_TABLES_READ
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). | ||||
| DATA(ld_plan_request) | = 'P'. | |||
Search for further information about these or an SAP related objects