Synchronization between SAP Travel Planning and Connected Reserv (SAP Library

Synchronization between SAP Travel Planning and Connected Reservation System

The SAP Travel Planning guarantees the comprehensive synchronization of travel plans in the SAP system with the respective current data from the connected reservation system. This covers both the online and the offline synchronization of data.

This synchronization is an important prerequisite for the consideration of modifications to posting records ( PNRs - Passenger Name Records), that have been carried out externally - outside the SAP system. This is, for example, the case if the reservation of a flight on a waiting list is confirmed in the reservation system or if the traveler changes the booking at the airport directly. So that the SAP system always has the same status of data as the connected reservation system, the travel plans (the PNR) must be synchronized.

Online Synchronization

An online synchronization is always carried out automatically each time a travel plan is called in the SAP system in editing mode, as this creates an up-to-date PNR. This form of synchronization has a processing limit. Three days after the end of the trip the PNR can no longer be called up in the reservation system. The PNR can also no longer be read in SAP Travel Planning and can only be called in display mode.

Offline Synchronization

As the AMADEUS Global Travel Distribution reservation system is connected to SAP Travel Planning, the AMADEUS-specific function AMADEUS Interface Record (AIR) is available for offline synchronization.

The offline synchronization has the following advantages:

A constant synchronization of the PNR is guaranteed using AIR A renewed call of the travel plan to trigger the synchronization with the data in the reservation system is no longer necessary.

Using the AIR it does not matter that a PNR can not be called in the connected reservation system after three days have elapsed . There are thus no time restrictions for the synchronization of a travel plan.

There is no authorization problem for bookings created externally: If a PNR has been created for an employee by a sales office unknown to the SAP system (that is, external to the SAP system, such as a travel agency) the SAP Travel Planning sales office does not have the authorization to read/edit this booking. A travel plan can not be created from such a booking. This authorization problem does not exist for the AIR offline synchronization if the SAP Travel Planning sales office is stored in a FC element in the externally created PNR.

Þ The SAP Travel Planning data allows an accurate reporting. As information about the externally created or externally modified bookings can be included, the SAP Travel Planning reporting data is comprehensive and reliable.

Prerequisites

Software prerequisites

To carry out the AIR import, you must install the AMADEUS ProPrinter ^® function. This software is available free of charge via the Internet or is delivered (also free of charge) with the installation of the AMADEUS Gateway software. The ProPrinter ^® must be installed on the same server as the RFC server.

For more information about the contact to the SAP & AMADEUS Competence Center, see the SAP Library under Financials ® Financial Accounting (FI) ® Travel Management ® Travel Planning ® Technical Prerequisites for Travel Planning.

Customizing prerequisites

The AIR (AMADEUS Interface Record) is created based on a ticket: Once a ticket has been issued, the reservation system sends the AIR to the sales office that created the travel plan and therefore also the PNR. An up-to-date AIR containing the necessary price and travel information is created each time the PNR is modified.

You specify the sales offices in the Customizing for Travel Management under Travel Planning ® Master Data ® Control Parameters for Travel Planning ® Define API access parameters.

If an office ID is stored in the Sales office (Settlement) field, the system takes this as the relevant SAP Travel Planning sales office.

If no entry exists in this field, the system identifies the office ID in the Sales office (Booking) field as the correct sales office.

If there is no entry in this field either, an offline synchronization of externally created bookings is not possible in SAP Travel Planning. In this case only external modifications of the PNR can be processed in the SAP system.