Auto Exchange And Refund

Please note that this service is restricted to SabreSonicRes-based airline customers.

Additional related functions include irregular operations such as involuntary reroute, schedule change and no coupon situations. For a Sabre hosted carrier, these functions are based in whole or in part on the information stored in the Virtual Coupon Record ( VCR) electronic ticketing database, the manually provided ticket information (if no electronic record is available), the itinerary in the Agent Assembly Area ( AAA), the fares filed in the Sabre GDS, the historical fare information and related CAT31 rules as filed with Sabre, the tables configured in the Sabre GDS such as the options table and the form number table and any override parameters that are part of the XML request. AER relies on the binary security token obtained on a prior call to SessionCreateRQ.

The AER web service uses the AER package in TPF to complete AER transactions. Generally, a transaction is priced and retained and if the price satisfies the customer, the transaction is then fulfilled. Depending on whether an exchange is requested or a refund is requested and whether the result requires additional money to be collected or a refund to be issued, different documents are generated (eg electronic ticket, refund receipt, voucher, etc.). When issuing a ticket, AER updates the AAA with the TE line for electronic tickets. When retaining a price, AER updates the AAA with the price quote record. Exchange pricing and fulfillment requires the AAA to contain the new itinerary. This may be accomplished outside of the AER web service. Refunds and exchanges require a document to exchange. Electronic documents may be referred to by document number. Manual documents require data entered in the XML request. Manual pricing requests require a AAA with new itinerary data.

The response to pricing requests include the ticketing data (if exchanging or refunding) as well as the pricing result data including the comparison data. Messages that would have come from TPF AER are also included in the response. Fulfillment request responses include the new document number as well as the pricing data. Data in the XML is limited to what's provided in the TPF data transmission record. The XML contains most of the TPF data transmission record fields.

For Ticketing to provide support to a carrier when using Ticketing web services such as MISCServicesRQ and AERRQ, the carrier needs to provide access credentials almost identical to what the carrier will use to access the web service. The ID should be robotic, contain a non-expiring password, be able to issue tickets and be present in RES (production), CERT (certification) and TSTS (integration). Recommended, but not required: ID should be created inactive in RES; ID should be given duty code Cross of Lorraine.

The ID will be used in the automated regression test suite and will be used when researching questions and problems. Once Ticketing receives the ID, Ticketing will request allocation of a TAM pool and the associated ICE security attributes for accessing the web service.