Vous êtes sur la page 1sur 5

ACS Support for Flight

History

BUSINESS
REQUIREMENTS
Version 1
29 October, 2004

2005, Sabre Inc. All rights reserved.


This documentation is the confidential and proprietary intellectual
property of Sabre Inc. Any unauthorized use, reproduction,
preparation of derivative works, performance, or display of this
document, or software represented by this document, without the
express written permission of Sabre Inc. is strictly prohibited.
Sabre and the Sabre logo design are trademarks and/or service
marks of an affiliate of Sabre Inc. All other trademarks, service
marks, and trade names are owned by their respective
companies.

Table of Contents

1.

INTRODUCTION............................................................................................................................................................... 1

2.

BUSINESS OBJECTIVES ................................................................................................................................................. 1

3.

AIRPORT PROCESSING SELECT FROM SIMILAR NAME LIST ....................................................................... 1

4.

AIRPORT PROCESSING NEW FUNCTIONALITY ................................................................................................. 2

5.

TRAINING AND ACTIVATION...................................................................................................................................... 2


Training Requirements.......................................................................................................................................................... 2
Activation Requirements ....................................................................................................................................................... 2

1.

Introduction
ACS passenger history records changes to flight and passenger items during the
check-in process. When a check-in entry produces a similar name list, the follow-up
entry consists of choosing from that list. History only saves the follow-up entry, not
the original entry. In order to record the action taken in this situation, the original
entry should be recorded to history.

2.

Business Objectives
The objective of this project is to save the entry that produced the similar name list.

3.

Airport Processing Select from Similar Name List

Example:
1. The check-in entry produces a similar name list
G-845Y-ROD
LB
845 29OCT
1 RODRIGUES
2 RODRIGUEZ

CBB 2
JORGE
JORGE

1235P 72T
Y
VVI
Y
VVI

PASSENGER LIST C0Y2


F NB TKT
F NB TKT

2. The follow-up entry consists of selecting the passenger from the list
G-1
LB
845
29OCT
CBB
2
1235P 72T
1
RODRIGUES JORGE
Y VVI
5A*F NB TKT
FLIGHT COUPON ATTACHED TO BOARDING PASS BY
HDQ87RX
3. Only the follow-up entry is saved in passenger history
G*HN/845/RODRIGUES
CITY
AGT DATE TIME LNIATA HISTORY ITEM
CBB /HDQ 87RX 29OCT 1007 A51419 G-1
CSEXQG RODRIGUES JORGE VVI
5A* NB TKT

__________________________________________________________________________________________
Page 1

4.

Airport Processing New Functionality

When an entry in ACS produces a similar name list, both the original entry and the followup entry should be saved in passenger history
G*HN/845/RODRIGUES
CITY
AGT DATE TIME LNIATA HISTORY ITEM
CBB /HDQ 87RX 29OCT 1006 A51419 G-1::G-845-ROD
CSEXQG RODRIGUES JORGE VVI
5A* NB TKT

5.

Training and Activation

Training Requirements

Airline Passenger Solutions airlines will be responsible for disseminating this


information.

Activation Requirements

This will be a global implementation.

__________________________________________________________________________________________
Page 2

Vous aimerez peut-être aussi