Importing AIRs (TP10) 

Use

The transaction TP10 Synchronization of Travel Plans via AMADEUS Interface Records (AIR) imports the AIRs from the directory created on the server by ProPrinter ® into the SAP system.

This transaction also automatically processes the AIRs that can be directly assigned to a SAP travel plan (because they could be identified unambiguously via personnel and trip number).

Unambiguous identification of AIRs

An unambiguous identification is possible for AIRs that relate to a booking created with SAP Travel Planning and that was just modified externally. For bookings created externally to the SAP system (PNRs) the personnel number can be sent in the PNR, via the "customer profile" stored in the AMADEUS system, so that a booking created externally can also be immediately identified and processed automatically. The important thing is that the trip number and/or the personnel number of the traveler is known in the AIR.

  Exception

This automatic processing of AIRs does not take place if the travel plan to be updated is locked at the time of the import. This would be the case if a travel plan was, for example, called for editing.

For the AIRs that can not be unambiguously processed and integrated in a travel plan, you must start the processing manually using transaction TP12.

Successful processing of AIRs

An AIR that has been processed successfully does not appear in the list of AIRs to be processed in TP12.

For more information about the processing status of an AIR see Displaying Success of AIR Processing.

The AIRs that could be processed are deleted from the SAP database automatically. In the AIR directory created by ProPrinter ® on the API server these AIRs are moved from the directory of AIRs to be processed to a backup directory automatically.

Procedure

  1. Create a batch job that will carry out the import of AIRs using TP10, for example, every night.
  2. Start transaction TP12.

Here you see a list of the AIRs that could not be identified and processed during the import. You now have to process these AIRs manually ( TP12).

Result

You have imported all the AIRs from the ProPrinter ® directory into the SAP system. The AIRs that could be identified were processed automatically and the corresponding travel plans updated. You have to process the AIRs that could not be identified manually using TP12.