SAP BAPI_TRIP_COLLECT_MILEAGE Function Module for Determination of Trip Legs for Employee
BAPI_TRIP_COLLECT_MILEAGE is a standard bapi trip collect mileage SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determination of Trip Legs for Employee processing and below is the pattern details for this FM, 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 bapi trip collect mileage FM, simply by entering the name BAPI_TRIP_COLLECT_MILEAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRTR
Program Name: SAPLHRTR
Main Program: SAPLHRTR
Appliation area: P
Release date: 09-Aug-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_TRIP_COLLECT_MILEAGE 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 'BAPI_TRIP_COLLECT_MILEAGE'"Determination of Trip Legs for Employee.
EXPORTING
EMPLOYEENUMBER = "Personnel Number
FROM_DATE = "Beginning Date of Selection Interval
TO_DATE = "End Date of Selection Interval
* VEH_TYPE = "Vehicle Type
* VEH_CLASS = "Vehicle Class
IMPORTING
RETURN = "Return Structure
TABLES
MILEAGE = "Trip Segments
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLHRTRV_STAT_001
EXIT_SAPLHRTRV_STAT_002
IMPORTING Parameters details for BAPI_TRIP_COLLECT_MILEAGE
EMPLOYEENUMBER - Personnel Number
Data type: BAPIEMPL-PERNROptional: No
Call by Reference: No ( called with pass by value option)
FROM_DATE - Beginning Date of Selection Interval
Data type: BAPITRIP-DEP_DATEOptional: No
Call by Reference: No ( called with pass by value option)
TO_DATE - End Date of Selection Interval
Data type: BAPITRIP-DEP_DATEOptional: No
Call by Reference: No ( called with pass by value option)
VEH_TYPE - Vehicle Type
Data type: BAPITRVMIL-VEH_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
VEH_CLASS - Vehicle Class
Data type: BAPITRVMIL-VEH_CLASOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_TRIP_COLLECT_MILEAGE
RETURN - Return Structure
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_TRIP_COLLECT_MILEAGE
MILEAGE - Trip Segments
Data type: BAPITRVMILOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_TRIP_COLLECT_MILEAGE 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_return | TYPE BAPIRETURN, " | |||
| lt_mileage | TYPE STANDARD TABLE OF BAPITRVMIL, " | |||
| lv_employeenumber | TYPE BAPIEMPL-PERNR, " | |||
| lv_from_date | TYPE BAPITRIP-DEP_DATE, " | |||
| lv_to_date | TYPE BAPITRIP-DEP_DATE, " | |||
| lv_veh_type | TYPE BAPITRVMIL-VEH_TYPE, " | |||
| lv_veh_class | TYPE BAPITRVMIL-VEH_CLAS. " |
|   CALL FUNCTION 'BAPI_TRIP_COLLECT_MILEAGE' "Determination of Trip Legs for Employee |
| EXPORTING | ||
| EMPLOYEENUMBER | = lv_employeenumber | |
| FROM_DATE | = lv_from_date | |
| TO_DATE | = lv_to_date | |
| VEH_TYPE | = lv_veh_type | |
| VEH_CLASS | = lv_veh_class | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| MILEAGE | = lt_mileage | |
| . " BAPI_TRIP_COLLECT_MILEAGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_TRIP_COLLECT_MILEAGE
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 BAPIEMPL INTO @DATA(ld_employeenumber). | ||||
| "SELECT single DEP_DATE FROM BAPITRIP INTO @DATA(ld_from_date). | ||||
| "SELECT single DEP_DATE FROM BAPITRIP INTO @DATA(ld_to_date). | ||||
| "SELECT single VEH_TYPE FROM BAPITRVMIL INTO @DATA(ld_veh_type). | ||||
| "SELECT single VEH_CLAS FROM BAPITRVMIL INTO @DATA(ld_veh_class). | ||||
Search for further information about these or an SAP related objects