!--a11y-->
Checking Flight Seat Availability 
A travel agency uses the integration scenario CheckFlightSeatAvailability to check the seat availability of a flight with an airline.
This addresses various technical concepts, depending on the configuration of the integration scenario. The following variants are supported for this integration scenario:
· Checking Flight Seat Availability (Proxy-to-Proxy)
The most important characteristics of this variant are: synchronous message exchange, does not use mappings, uses proxy runtime.
· Checking Flight Seat Availability (Proxy-to-RFC)
The most important characteristics of this variant are: synchronous message exchange, uses mappings, uses the RFC adapter.
· Checking Flight Seat Availability (Proxy-to-Web Service)
The most important characteristics of this variant are: synchronous message exchange, calls a Web service, uses the SOAP adapter.
For more information about the business uses of the integration scenario, see Business Description (CheckFlightSeatAvailability).
For more information about the concepts, configuration, and execution of the integration scenario, see the descriptions of the respective variants.