When
SAP Travel Planning
is used with the reservation system of AMADEUS Global Travel Distribution, the following elements are involved in the communication between the SAP system and the Amadeus system:
SAP system
SAP Gateway
Amadeus Gateway
API server
Amadeus central system (Amadeus Practice Training or Amadeus Production)
The system infrastructure is as follows:
The RFC destination ( Remote Function Call) represents the logical connection between the SAP system and the Amadeus Gateway. The RFC calls are channeled through the SAP Gateway. The SAP Gateway communicates with the Amadeus Gateway. Within the client/server architecture, the SAP system takes on the role of the client and the Amadeus Gateway the role of the server.
The Amadeus Gateway's task is the identification at the Amadeus API server. The API server controls access to the respective Amadeus central system (
Amadeus Practice Training
or
Amadeus Production
). Communication between the Amadeus Gateway and the Amadeus API server is based on RPC calls (
Remote Procedure Calls
). Here the Amadeus Gateway takes on the role of the client and the Amadeus API server the role of the server.
Note
For the latest information on the installation procedures, see SAP Service Marketplace at
.See also:
RFC destination for Travel Planning: See the Implementation Guide (IMG) for Travel Management under
.For general information on communication between SAP and external programs, see
under: