SAP BAPI_FLCONN_GETDETAIL Function Module for Find details about a flight connection
BAPI_FLCONN_GETDETAIL is a standard bapi flconn getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find details about a flight connection 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 flconn getdetail FM, simply by entering the name BAPI_FLCONN_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAPBC_BAPI_SFLCONN
Program Name: SAPLSAPBC_BAPI_SFLCONN
Main Program:
Appliation area:
Release date: 26-Sep-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_FLCONN_GETDETAIL 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_FLCONN_GETDETAIL'"Find details about a flight connection.
EXPORTING
TRAVELAGENCYNUMBER = "Travel Agency Number
CONNECTIONNUMBER = "Flight connection number at travel agency
FLIGHTDATE = "Departure date
* NO_AVAILIBILITY = ' ' "No availability required
IMPORTING
CONNECTION_DATA = "Connection data
PRICE_INFO = "Prices
TABLES
* EXTENSION_IN = "Import customer enhancements
* FLIGHT_HOP_LIST = "Route segment
* AVAILIBILITY = "Availability
* EXTENSION_OUT = "Export customer enhancements
* RETURN = "Return Messages
IMPORTING Parameters details for BAPI_FLCONN_GETDETAIL
TRAVELAGENCYNUMBER - Travel Agency Number
Data type: BAPISCOKEY-AGENCYNUMOptional: No
Call by Reference: No ( called with pass by value option)
CONNECTIONNUMBER - Flight connection number at travel agency
Data type: BAPISCOKEY-FLIGHTCONNOptional: No
Call by Reference: No ( called with pass by value option)
FLIGHTDATE - Departure date
Data type: BAPISCOKEY-FLIGHTDATEOptional: No
Call by Reference: No ( called with pass by value option)
NO_AVAILIBILITY - No availability required
Data type: BAPISTRAUX-NO_AVAILDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_FLCONN_GETDETAIL
CONNECTION_DATA - Connection data
Data type: BAPISCODATOptional: No
Call by Reference: No ( called with pass by value option)
PRICE_INFO - Prices
Data type: BAPISCOPRIOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_FLCONN_GETDETAIL
EXTENSION_IN - Import customer enhancements
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
FLIGHT_HOP_LIST - Route segment
Data type: BAPISCOHOPOptional: Yes
Call by Reference: Yes
AVAILIBILITY - Availability
Data type: BAPISCOAVAOptional: Yes
Call by Reference: Yes
EXTENSION_OUT - Export customer enhancements
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_FLCONN_GETDETAIL 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: | ||||
lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
lv_connection_data | TYPE BAPISCODAT, " | |||
lv_travelagencynumber | TYPE BAPISCOKEY-AGENCYNUM, " | |||
lv_price_info | TYPE BAPISCOPRI, " | |||
lt_flight_hop_list | TYPE STANDARD TABLE OF BAPISCOHOP, " | |||
lv_connectionnumber | TYPE BAPISCOKEY-FLIGHTCONN, " | |||
lv_flightdate | TYPE BAPISCOKEY-FLIGHTDATE, " | |||
lt_availibility | TYPE STANDARD TABLE OF BAPISCOAVA, " | |||
lt_extension_out | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
lv_no_availibility | TYPE BAPISTRAUX-NO_AVAIL, " SPACE | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
  CALL FUNCTION 'BAPI_FLCONN_GETDETAIL' "Find details about a flight connection |
EXPORTING | ||
TRAVELAGENCYNUMBER | = lv_travelagencynumber | |
CONNECTIONNUMBER | = lv_connectionnumber | |
FLIGHTDATE | = lv_flightdate | |
NO_AVAILIBILITY | = lv_no_availibility | |
IMPORTING | ||
CONNECTION_DATA | = lv_connection_data | |
PRICE_INFO | = lv_price_info | |
TABLES | ||
EXTENSION_IN | = lt_extension_in | |
FLIGHT_HOP_LIST | = lt_flight_hop_list | |
AVAILIBILITY | = lt_availibility | |
EXTENSION_OUT | = lt_extension_out | |
RETURN | = lt_return | |
. " BAPI_FLCONN_GETDETAIL |
ABAP code using 7.40 inline data declarations to call FM BAPI_FLCONN_GETDETAIL
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 AGENCYNUM FROM BAPISCOKEY INTO @DATA(ld_travelagencynumber). | ||||
"SELECT single FLIGHTCONN FROM BAPISCOKEY INTO @DATA(ld_connectionnumber). | ||||
"SELECT single FLIGHTDATE FROM BAPISCOKEY INTO @DATA(ld_flightdate). | ||||
"SELECT single NO_AVAIL FROM BAPISTRAUX INTO @DATA(ld_no_availibility). | ||||
DATA(ld_no_availibility) | = ' '. | |||
Search for further information about these or an SAP related objects