SAP MIB_TR_TRAVELCONFIG_SEARCH Function Module for MPAPPS: Travel Request: Travel request configuration search









MIB_TR_TRAVELCONFIG_SEARCH is a standard mib tr travelconfig search SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MPAPPS: Travel Request: Travel request configuration search 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 mib tr travelconfig search FM, simply by entering the name MIB_TR_TRAVELCONFIG_SEARCH into the relevant SAP transaction such as SE37 or SE38.

Function Group: MIB_TR
Program Name: SAPLMIB_TR
Main Program: SAPLMIB_TR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MIB_TR_TRAVELCONFIG_SEARCH 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 'MIB_TR_TRAVELCONFIG_SEARCH'"MPAPPS: Travel Request: Travel request configuration search
  EXPORTING
*  DATE =  "Beginning Date of Trip Segment
*  TIME =  "Beginning Time of Trip Segment
*  TZONE =  "Time Zone

TABLES
   TRAVEL_CONFIGURATION =  "Travel Request Configuration
   RETURN =  "Return Parameter
.



IMPORTING Parameters details for MIB_TR_TRAVELCONFIG_SEARCH

DATE - Beginning Date of Trip Segment

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

TIME - Beginning Time of Trip Segment

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

TZONE - Time Zone

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

TABLES Parameters details for MIB_TR_TRAVELCONFIG_SEARCH

TRAVEL_CONFIGURATION - Travel Request Configuration

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for MIB_TR_TRAVELCONFIG_SEARCH 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_date  TYPE REBED, "   
lt_travel_configuration  TYPE STANDARD TABLE OF MIB_S_TRAVEL_REQUEST_CONF, "   
lv_time  TYPE REBEU, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_tzone  TYPE TZNZONE. "   

  CALL FUNCTION 'MIB_TR_TRAVELCONFIG_SEARCH'  "MPAPPS: Travel Request: Travel request configuration search
    EXPORTING
         DATE = lv_date
         TIME = lv_time
         TZONE = lv_tzone
    TABLES
         TRAVEL_CONFIGURATION = lt_travel_configuration
         RETURN = lt_return
. " MIB_TR_TRAVELCONFIG_SEARCH




ABAP code using 7.40 inline data declarations to call FM MIB_TR_TRAVELCONFIG_SEARCH

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!