Connection to AMADEUS
When using R/3 Travel Planning with the reservation system from AMADEUS Global Travel Distribution the following elements are involved in the communication between the R/3 System and the Amadeus System:
The system infrastructure is as follows:
The RFC destination (
Remote Function Call) represents the logical connection between the R/3 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 R/3 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 the access to the respective Amadeus central system (Amadeus Practice Training or Amadeus Production). The communication between Amadeus Gateway and the Amadeus API server is carried out via 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.
For the latest information on the installation procedure in each case, see the SAP Service Marketplace under
http://service.sap.com/ ® Downloads & Services.
See also:
Amadeus Gateway SAP GatewayTravel Planning RFC destination:
See the Implementation Guide (IMG) for Travel Management under Travel Planning ® Master Data ® Control Parameters for Travel Planning ® RFC Destination.
For general information on the communication between R/3 and external programs, see Help ® SAP Library under:
Basis Components ® SAP Communication: CPI-C Programming ® Programming under Different Constellations ® Communication between R/3 and Externally Registered Program
Basis Components ® Basis Services / Communication Interfaces ® Remote Connections ® RFC Programming in ABAP ® Maintaining Remote Destinations