Import and Processing (SAP Library - Travel Planning (FI-TV-PL))

Import and Processing

Use

The synchronization of the travel plans in the SAP system with the externally modified data is achieved via the import and processing of AIRs (AMADEUS Interface Record). In the AIRs the currently up-to-date reservation and settlement data from the reservation is communicated to the SAP system (see Synchronization between SAP Travel Planning and Connected Reservation System).

The AIRs are stored in the AMADEUS Gateway. The AIRs are stored as files on the local PC via the ProPrinter ^® program that receives the AIRs sent by the reservation system. From there the AIRs can be imported into the SAP system for further processing.

Two transactions are available for this (you can not call these transactions from the menu):

Transaction code

Function

TP10

Imports the AIRs from the directory created on the server by ProPrinter ^® into the SAP system.

This includes:

the import of all AIRs into the SAP system

the automatic processing of the AIRs that can be unambiguously assigned to a travel plan (that is, for which the system can determine an exact personnel number and/or trip number)

See also Importing AIRs (TP10).

TP12

Processes the AIRs that could not be unambiguously assigned during the import. These include, for example, bookings created externally to the SAP system (PNRs), as a travel plan must first be created for these in SAP Travel Planning.

See also Processing AIRs and Updating Travel Plans (TP12)

The following graphic illustrates the points in the synchronization flow where the two transactions TP10 and TP12 occur.

Prerequisites

The data required for an exact identification of an AIR to a travel plan is the personnel number of the traveler and, for an external modification of a booking created in the SAP system, the trip number.

If a travel plan was created in the SAP system, this information is automatically contained in the PNR. During the synchronization activity the travel plan identified correspondingly is updated with new data.

If a travel plan was created outside the SAP system, then certain data must be specified in the PNR during the external creation so that the SAP system can process the AIR that belongs to it.

For this the address of the processing sales office must be specified in the PNR via an FC element. This is set up in the Customizing for SAP Travel Planning and is connected to the ProPrinter ^® .

The personnel number can be determined using one of the following methods:

The traveler's personnel number can be stored in his "customer profile" in the AMADEUS system. The information from the "customer profile" is automatically sent with a traveler's booking.

If the personnel number is not stored in the AMADEUS "customer profile", it is determined using the name of the traveler specified in the PNR. After importing the AIR the SAP system checks which employee corresponds to the name specified in the PNR and determines the corresponding personnel number.