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
Offline Synchronization, which can be completed on a regular basis (for example using a batch job), compares modifications to booking (PNRs) made outside of the SAP system with the internal SAP Travel Planning data and updates the information as required.
Depending upon the connected reservation system, certain programs are available to set up this synchronization. These are described in the following sections:
Synchronization with Amadeus Synchronization with Sabre