SAP FITV_RD_EXPORT_TRIPDATA Function Module for
FITV_RD_EXPORT_TRIPDATA is a standard fitv rd export tripdata 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 fitv rd export tripdata FM, simply by entering the name FITV_RD_EXPORT_TRIPDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITV_RCUR_DEST
Program Name: SAPLFITV_RCUR_DEST
Main Program: SAPLFITV_RCUR_DEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FITV_RD_EXPORT_TRIPDATA 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 'FITV_RD_EXPORT_TRIPDATA'".
EXPORTING
WA_PTP02 = "Personnel Number
WA_PERIO = "Structure of Transp. Table PTRV_PERIO
* PERNR = "Personnel Number
BEARB_STAT = "Single-Character Indicator
IMPORTING Parameters details for FITV_RD_EXPORT_TRIPDATA
WA_PTP02 - Personnel Number
Data type: PTP02Optional: No
Call by Reference: Yes
WA_PERIO - Structure of Transp. Table PTRV_PERIO
Data type: PTP42Optional: No
Call by Reference: Yes
PERNR - Personnel Number
Data type: PTP02-PERNROptional: Yes
Call by Reference: Yes
BEARB_STAT - Single-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FITV_RD_EXPORT_TRIPDATA 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_wa_ptp02 | TYPE PTP02, " | |||
| lv_wa_perio | TYPE PTP42, " | |||
| lv_pernr | TYPE PTP02-PERNR, " | |||
| lv_bearb_stat | TYPE CHAR1. " |
|   CALL FUNCTION 'FITV_RD_EXPORT_TRIPDATA' " |
| EXPORTING | ||
| WA_PTP02 | = lv_wa_ptp02 | |
| WA_PERIO | = lv_wa_perio | |
| PERNR | = lv_pernr | |
| BEARB_STAT | = lv_bearb_stat | |
| . " FITV_RD_EXPORT_TRIPDATA | ||
ABAP code using 7.40 inline data declarations to call FM FITV_RD_EXPORT_TRIPDATA
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 PTP02 INTO @DATA(ld_pernr). | ||||
Search for further information about these or an SAP related objects