SAP BAPI_TRIP_CHECK_STATUS Function Module for Establish Status of Trip

Search SAP Function Modules

BAPI_TRIP_CHECK_STATUS is a standard bapi trip check status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Establish Status of Trip 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 check status FM, simply by entering the name BAPI_TRIP_CHECK_STATUS 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_CHECK_STATUS 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_CHECK_STATUS'"Establish Status of Trip
  EXPORTING
   EMPLOYEENUMBER =  "Employee's Personnel Number
*  TRIPNUMBER =  "Trip Number of Employee Trip
*  DEPARTURE_FROM =  "Trip Departure Date (From)
*  DEPARTURE_TO =  "Trip Departure Date (To)
*  CALCULATE_AMOUNTS = ' ' "Calculation of Amounts (X/' ')
*  PERIODNUMBER = '000' "Number of Trip Period

 IMPORTING
   RETURN =  "Return Structure (Instead of Exceptions)

TABLES
   TRIPS =  "Table of Trips
*  AMOUNTS =  "Table of Different Trip Amounts

.

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_CHECK_STATUS

EMPLOYEENUMBER - Employee's Personnel Number

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

TRIPNUMBER - Trip Number of Employee Trip

Data type: BAPITRIP-TRIPNO
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEPARTURE_FROM - Trip Departure Date (From)

Data type: BAPITRIP-DEP_DATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEPARTURE_TO - Trip Departure Date (To)

Data type: BAPITRIP-DEP_DATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CALCULATE_AMOUNTS - Calculation of Amounts (X/SPACE)

Data type: BAPITRVXXX-BOOLEAN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PERIODNUMBER - Number of Trip Period

Data type: BAPITRVXXX-PERIOD
Default: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_TRIP_CHECK_STATUS

RETURN - Return Structure (Instead of Exceptions)

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

TABLES Parameters details for BAPI_TRIP_CHECK_STATUS

TRIPS - Table of Trips

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

AMOUNTS - Table of Different Trip Amounts

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

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

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