Ansicht
Dokumentation
Import and Processing of Reservation and Settlement Data from GDS ( RELNFI_46C_TV_PL_A0002 )
rdisp/max_wprun_time - Maximum work process run time General Material DataThis documentation is copyright by SAP AG.
Short text
Import and Processing of Reservation and Settlement Data from GDS
Use
The currentrelease ensures complete synchronization of travel plans between the connected reservation system AMADEUS and the SAP System.
This synchronization is above all significant in the following cases:
- External modification of a travel plan created in SAP Travel Planning
When a travel plan is booked with SAP Travel Planning, a PNR is created which contains all necessary information on the booking and the traveler. It is also possible for this PNR to be modified outside of the SAP System, if, for example, a traveler has a flight rebooking performed directly at the airport. These modifications can be transported back to the SAP System and then processed there.
- External creation of a booking for an employee
If a booking is made outside of SAP Travel Planning, an import also takes place to the SAP System and its processing for the relevant PNR, automatically creating a new travel plan for the employee identified by the PNR. This is only possible if a certain PNR element containing the target address for SAP Travel Planning was included when the external booking was made.
The import and processing of these data records takes place via the AMADEUS-specific functionality AIR (Amadeus Interface Record).
The AIR is a data record that contains all of the information relevant for booking that is needed to issue a ticket on the basis of a reservation. The reservation can have been made within or outside of the SAP System. Every time that a PNR is modified externally the current AIR is imported from the reservation system AMADEUS to the SAP System, where it is processed and the travel plans are updated.
Synchronization by means of AIRs brings the following advantages:
- Synchronization of PNRs via AIRs is guaranteed at all times. It is no longer necessary to call the travel plan again in order to trigger synchronization with the data in the reservation system. In past releases that was necessary.
- The usage of AIRs solves the problem that a PNR can no longer be called in the connected reservation system three days after completion of the last booked segment. This eliminates all time restrictions on the availability of a travel plan.
- Complete synchronization by means of the AIR ensures accurate Reporting. The data in Travel Planning is 100% available for reliable reporting.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
You can import the AIR regularly via a simple batch job.
To be able to execute the AIR import, you have to install the AMADEUS functionality ProPrinter. This software can be obtained free of charge via the internet or - also free of charge - it can be supplied when the AMADEUS Gateway Software is installed. For more information on contacting the SAP & AMADEUS Competence Center see the documentation in the SAP Library under Financials → Financial Accounting → Travel Management → Travel Planning → Technical Prerequisites for Travel Planning.
Effects on Customizing
Further Information
For more information see the SAP Library under Financials → Financial Accounting → Travel Management → Travel Planning → Synchronization of Posting with Data from the Reservation System.
ROGBILLS - Synchronize billing plans PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 4296 Date: 20240520 Time: 200941 sap01-206 ( 87 ms )
