SAP PTRA_UTIL_MILEAGE_GET Function Module for

Search SAP Function Modules

PTRA_UTIL_MILEAGE_GET is a standard ptra util mileage get 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 ptra util mileage get FM, simply by entering the name PTRA_UTIL_MILEAGE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: PTRA_UTIL_MILEAGE
Program Name: SAPLPTRA_UTIL_MILEAGE
Main Program: SAPLPTRA_UTIL_MILEAGE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PTRA_UTIL_MILEAGE_GET 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 'PTRA_UTIL_MILEAGE_GET'"
  EXPORTING
   I_EMPLOYEENUMBER =  "Personnel Number
   I_TRIPNUMBER =  "Trip Number
*  I_PERIODNUMBER =  "Number of Trip Period
*  I_PERIODVERSION =  "Sequential Number of Period
*  I_TRIP_SCHEMA =  "Language Key
*  I_TRIP_ACTION = 'MOD' "Checkbox
*  I_TRIP_COMPONENT =  "Plan Request Indicator
*  I_TRIP_TCODE = 'WEBE' "Dependent screen number for field control
*  I_LANGUAGE = SY-LANGU "Language Key

 IMPORTING
   E_HEAD =  "General Information and Period Data of a Trip
   ET_KMVER =  "Legs of Trip
   E_KMVER_DEFAULT =  "
   ET_EDITOR =  "Table for DB Structure PTP71
   ET_EDITOR_DEFAULT =  "Table for Structure for Default Values Text Information

EXCEPTIONS
   ERROR_OCCURRED = 1 

.

IMPORTING Parameters details for PTRA_UTIL_MILEAGE_GET

I_EMPLOYEENUMBER - Personnel Number

Data type: BAPIEMPL-PERNR
Optional: No
Call by Reference: Yes

I_TRIPNUMBER - Trip Number

Data type: BAPITRIP-TRIPNO
Optional: No
Call by Reference: Yes

I_PERIODNUMBER - Number of Trip Period

Data type: BAPITRVXXX-PERIOD
Optional: Yes
Call by Reference: Yes

I_PERIODVERSION - Sequential Number of Period

Data type: PTRV_PERIO-PDVRS
Optional: Yes
Call by Reference: Yes

I_TRIP_SCHEMA - Language Key

Data type: HEAD_PERIO-SCHEM
Optional: Yes
Call by Reference: Yes

I_TRIP_ACTION - Checkbox

Data type: PTRV_TRIP_ACTION_M
Default: 'MOD'
Optional: Yes
Call by Reference: Yes

I_TRIP_COMPONENT - Plan Request Indicator

Data type: PLAN_REQUEST
Optional: Yes
Call by Reference: Yes

I_TRIP_TCODE - Dependent screen number for field control

Data type: RDYNNU
Default: 'WEBE'
Optional: Yes
Call by Reference: Yes

I_LANGUAGE - Language Key

Data type: BAPITRVXXX-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PTRA_UTIL_MILEAGE_GET

E_HEAD - General Information and Period Data of a Trip

Data type: HEAD_PERIO
Optional: No
Call by Reference: Yes

ET_KMVER - Legs of Trip

Data type: PTRV_UTIL_KMVER_T
Optional: No
Call by Reference: Yes

E_KMVER_DEFAULT -

Data type: PTRV_UTIL_KMVER
Optional: No
Call by Reference: Yes

ET_EDITOR - Table for DB Structure PTP71

Data type: PTRV_UTIL_EDITOR_T
Optional: No
Call by Reference: Yes

ET_EDITOR_DEFAULT - Table for Structure for Default Values Text Information

Data type: PTRV_UTIL_EDITOR_DEFAULT_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURRED - Errors have occurred

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PTRA_UTIL_MILEAGE_GET 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.

ABAP code using 7.40 inline data declarations to call FM PTRA_UTIL_MILEAGE_GET

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.

Search for further information about these or an SAP related objects