Basic Sabre Formats and Functions
Table of Contents
- Objectives
- Overview
- Working in the Sabre System
- Introduction to the Travel Agency Environment
- Sabre Keyboard
- Sign-in and Sign-out
- Passcode Guidelines
- Sign-out
- Sabre Work Areas
- City Pair Availability
- Encode/Decode, Sabre Atlas
- Display City Pair Availability
- Sell From City Pair Availability
- Flight Information
- Insert and Cancel Segments
- Create and Modify Passenger Name Records
- Itinerary
- Name Field
- Phone Field
- Ticketing Field
- Received From Field
- Optional PNR Data
- Remarks Field
- Address Fields
- Passenger E-Mail Address Field
- Frequent Traveler Numbers
- OSI (Other Service Information)
- SSR (Special Service Request)
- DK Number Field in PNR
- Divide, Increase/Reduce, and Clone PNRs
- Divide PNR
- Increase Number in Party
- Reduce Number in Party
- Clone PNR Data
- Sabre Replay
- Common Calls and Error Responses
- Additional References
© 2006 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. Basic Sabre Formats and Functions Training Guide November 2006 Table of Contents 2
Sabre, the Sabre logo design and Personal Trainer 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.
Objectives
Upon completion of this course, you will understand:
• The importance of providing software support to subscribers
• Fundamental
Sabre
keyboard functions
• Sign in/Sign out formats and guidelines
• City pair availability displays and formats
• How to build and modify passenger reservations
• How to use the
Sabre
Replay function
Overview
Sabre Holdings recognizes the importance of providing our travel agent
customers the
functionality and product support necessary to provide comprehensive
travel services to their clients. Global Customer Support Center
specialists must understand
Sabre
global
distribution system functions and learn various formats to be
adequately prepared to support calls from our valued subscribers.
You will be presented with a wide range of questions and problem
solving challenges from subscribers with various backgrounds and levels
of experience. You will diagnose problems, advise formats and solutions,
assist with business tools, and escalate issues when necessary. While
providing the requested technical assistance, Software Support
specialists are also expected to demonstrate excellent customer service
skills. It is important that you become familiar with the wide range of
Sabre
products and services in order to successfully provide software
helpdesk assistance.
During this training course, we will cover topics to help you learn
procedures and troubleshooting techniques in order to deliver our products and services to the
travel agency community. You will be introduced to basic concepts and
continually build upon that foundation during and after classroom
instruction. You will gain the knowledge and
background needed to become proficient and successful as a Customer
Support Specialist.
Workinginthe Sabre System
Travel agents access
Sabre
functions by various point of sale solutions:
Sabre for Windows,
MySabre, and
Turbo Sabre.
You will work primarily in host
Sabre
and learn skills that
prepare you to support our subscribers regardless of which application
they use.
Sabre for Windows
has been the most common method of access and it is currently used
by
most of our Software Support specialists. However, more and more
customers are migrating
to
MySabre
so it is important that you become capable of working in both
systems.
Introduction to the Travel Agency Environment
The travel agencies of today provide a wide variety of services to the
traveling public. They
demand more than just air travel. Car, hotel, cruise, train, and tour
reservations are also required.
In the past, most services had to be obtained by telephoning the
various vendors for schedules, availability, and reservations. With the onset of Computer
Reservation Systems (CRS), these services may be obtained in seconds, with minimal need for
phone calls. Our
Sabre
customers subscribe to the most sophisticated computerized reservation
system on the market. The
Sabre
system is the gateway to the world of travel and
travel-related services.
Sabre
is a mainframe CRS system located underground in Tulsa, Oklahoma. It
was installed in Briarcliff Manor, NY in 1963, and was made widely available to the
travel industry in 1976.
Sabre
is the largest non-government real time system, second only to the
system maintained by the US government.
This student reference will provide information to familiarize you with
the terminology and concepts of the agency environment as they pertain to
Sabre. It will also provide the tools necessary to service clients in a professional and timely manner, which
will be profitable and beneficial to you and our customers.
Some amazing statistics:
• More than 41,000 travel agencies in 112 countries use
Sabre
• More than $71 million in travel is booked through
Sabre
each year
• More than 400 million bookings per year
• Approximately 36% of all reservations made in the world are booked
through
Sabre
• More than 440 airline carriers
• More than 42,000 hotel properties
• More than 50 car rental companies
• Has an average response time of under 3 seconds
• At its peak, processes more than 7,300 messages per second
Sabre Keyboard
You must become familiar with the keys and functions of the Sabre
keyboard in order to
effectively perform your job responsibilities. You will also be called
upon to offer keyboard
guidance and direction to customers while providing technical
support.
Definition of “Cursor”
A blinking character on the Sabre screen which indicates placement of
the next character to be typed.
Parts of the Keyboard
|
Component |
Function |
|
PF keys |
Also called programmable function |
|
Numeric key pad |
Functions as a calculator. |
|
Arrow keys |
Used to move the cursor up, down, left and |
|
Insert / Delete keys |
Used to insert or delete a space or |
|
Erase key |
Erases the character to the left of the |
|
CTRL key |
When depressed in conjunction with another |
|
ALT key |
When depressed in conjunction with another |
Identification Code Keys
The first row of the keyboard allows you to create or display a Passenger
Name Record
(PNR). The keys are labeled with codes to identify their function. Below is
an illustration
and explanation of the Identification Code Keys (ICK)
|
Code |
Label |
Function |
|
1 |
AVAIL |
Request City Pair Availability |
|
2 |
FLIFO |
Request Flight Information |
|
3 |
GFAX |
Request special services or information on other airlines |
|
4 |
FAX |
Request special services or information on American Airlines |
|
5 |
RMKS |
Add remarks information |
|
6 |
RCVD |
Add received from |
|
7 |
TKT |
Add ticketing field |
|
8 |
TL |
Add time limit for ticketing |
|
9 |
FONE |
Add telephone number |
|
0 |
SEG |
Sell from Air, Car, or Hotel availability display |
|
- |
NAME |
Add passenger name |
|
* |
DSPLY |
Display Passenger Name Record (PNR) |
Sign-in and Sign-out
The first step to using the Sabre system is to sign in. For initial
sign, in you will input a
generic password provided by your instructor. It is placed in the current
passcode field, and you then press enter to sign in. This will be your
current passcode the next time you sign in. To change your passcode: Input
your current passcode, tab to the new passcode field, input your new
personal passcode, and press enter. This will sign you into the system and
your passcode will be changed. For security purposes, the passcode will not
appear on the screen. You will always use your assigned ID number and the
passcode that you create.
Sign In
|
Task |
Format Example |
|
|
1 |
Type SI* followed by your agent |
SI*(ID Number) |
|
2 |
Type your passcode in the sign-in mask.
(7-8 alpha-numeric characters required) |
TEXT012 |
Example Response
AGENT SIGN IN
01 CURRENT
PASSCODE
02 ID <941032>
03
SUF <AAS>
04 DUTY CODE <.> 05 AREA <*> NEW
PASSCODE
Components of the Sign-in Mask
|
NBR |
Component |
Function |
|
01 |
CURRENT PASSCODE |
An area where you type your current passcode. |
|
02 |
ID |
Reflects your agent identification number. |
|
03 |
SUF |
Reflects an agency’s location – pseudo city code |
|
04 |
DUTY CODE |
Reflects duty code or level of access. |
|
05 |
AREA |
Reflects the area to be signed-in. |
|
06 |
NEW PASSCODE |
An area where you can change your passcode. |
Passcode Guidelines
You are required to create and periodically change personal passcodes. The
following
guidelines meet company security mandates:
• Must be a minimum of seven, and a maximum of eight characters.
• Cannot contain “Q” or “Z” or proper names and words such as Sabre, Dallas,
Marie, or
Joe.
• Must contain at least one alpha and one numeric character.
• Cannot include more than 2 repeating characters.
Example: AA1BB12 is correct; 111AA22 is not acceptable.
• Sabre employees must change their passcode every 45 days (every 90
days for external
customers) and cannot use the last 4 passcodes.
• Users will be locked out after 6 invalid sign in attempts.
• You must establish a Personal Identification Number (PIN). This
will allow you to
reestablish a new passcode if you forget or are locked out.
To Establish a PIN:
• Enter PIN HELP for guidelines to establish a PIN or to change a
passcode
• Once signed in, type H/PIN
• Follow the instructions to enter your PIN. If accepted, the response
is
- PIN ESTABLISHED –
Basic Sabre Formats and Functions Training Guide November 2006 Sabre Work
Areas 9
PIN Criteria:
• PIN must be four numeric characters and cannot be all zeros
• PIN cannot contain the same sequence of numbers as your sign-in ID
• You are responsible for maintaining the privacy and confidentiality of
your PIN
• Once assigned, you *CANNOT* change your PIN
Sign-out
|
Task |
Format Example |
|
Sign out of current work area |
SO |
|
Sign out of all work areas |
SO* |
Sabre Work Areas
After signing into Sabre, the following entries can be made to change
or display your work area.
|
Task |
Format Example |
|
Change to a different work area |
(work area letter) |
|
Display current work area |
*S |
|
Display the status of all working areas |
*S* |
|
Display the status of all working areas |
*S*P |
|
Redisplay sign-in message |
S/ |
City Pair Availability
City Pair Availability (CPA) is a display of flight times and seats offered
between a specific
city pair. CPA is used by travel agents on a daily basis to view flights
operated by various
carriers. Agents must use the 3 letter airport or city codes to make these
entries. Sabre offers
encoding and decoding formats to determine the appropriate codes.
Encode/Decode , Sabre Atlas
Encoding
|
Task |
Format Example |
|
Encode city name |
W/-CC(city name) |
|
Encode airport name |
W/-AP(airport name) |
|
Encode airline name |
W/-AL(airline name) |
|
Encode car rental company |
W/-CR(car rental name |
|
Encode hotel chain |
W/-HL(hotel name) |
|
Encode aircraft type |
W/EQ-(aircraft type) |
|
Encode travel agency name |
W/-TA(agency name) |
Decoding
|
Task |
Format Example |
|
Decode city/airport code |
W/*(city code) |
|
Decode airline code |
W/*(airline code) |
|
Decode car rental company code |
W/CR*(car rental company code) |
|
Decode hotel chain code |
W/HL*(hotel chain code) |
|
Decode aircraft type code |
W/EQ*(aircraft type code) |
|
Decode agency pseudo city code |
W/*(agency pseudo city code) |
SABRE ATLAS
|
Task |
Format Example |
|
Display the 10 closest airports to a |
W/-CY(city name),(state code) |
|
Display the 10 closest airports to a |
W/-CY(city name),(country code) |
|
Display the 10 closest airports to a |
W/-AT(three-letter airport code) |
|
Display the 10 closest airports to a |
W/-MB(name of military base),(optional |
|
Display the distance between two |
W/-AT(three-letter airport code) |
DISPLAY FROM SIMILAR NAME LIST
A similar name list displays when the state or country code are not specified. Use theseformats to display a similar name list when there is no exact match.
|
Task |
Format Example |
|
|
1 |
Encode city name format used with no state or |
W/-CY(city name |
|
2 |
Select from the list displayed |
W/-SL(line number) |
|
Redisplay the last similar name list |
W/-SL* |
Display City Pair Availability
CPA and Flight Information displays are possible once the appropriate city
or airport codes are determined.
|
Task |
Format Example |
|
Request availability |
1(travel date)(departure city)(arrival |
One letter codes can appear in a City Pair Availability display to indicate
the carrier’s
operating day(s) of the week. They may appear to the right of the number of
stops. In the
example below, XJ indicates except Saturday. When there is no day of service
indicator this
means the flight operates daily.
Basic Sabre Formats and Functions Training Guide November 2006 City Pair
Availability 12
Note: When a travel agency displays a CPA without specifying an airline, the
carriers with
service on the requested routing are displayed. CPA entries made from FSG
default
to AA when no airline is specified.
Example: CPA Responses (from a travel agency)
.png)
If two meal codes are listed together, both meals are served in in-flight.
If meal codes are separated by a slash, the first meal is served in premium
class and the second meal is served in coach class. Some frequently seen
meal codes are listed below. Type DU*/MLS to display a more complete
listing.
Meal Codes
|
Code |
Description |
Code |
Description |
|
B |
Breakfast |
K |
Continental breakfast |
|
L |
Lunch |
S |
Snack |
|
D |
Dinner |
M |
Meal |
|
F |
Food for purchase |
G |
Food/beverage purchase paid by |
Days of Week Codes
|
Code |
Number |
Description |
Code |
Number |
Description |
|
M |
1 |
Monday |
T |
2 |
Tuesday |
|
W |
3 |
Wednesday |
Q |
4 |
Thursday |
|
F |
5 |
Friday |
J |
6 |
Saturday |
|
S |
7 |
Sunday |
Availability Shortcuts
|
Task |
Format Example |
|
Request additional flight availability |
1* |
|
Redisplay last availability |
1*R |
|
Change the departure time |
1*(time) |
|
Add specified number of days to availability date |
1‡(number of days) |
|
Subtract specified number of days to availability date |
1-(number of days) |
|
Change arrival city |
1*A(city code) |
|
Change departure city |
1*D(city code) |
|
Task |
Format Example |
|
Change city pair and keep original day and time |
1*(city code)(city code) |
|
Redisplay original availability |
1*OA |
|
Display additional classes of service |
1*C |
Requesting Return Availability
|
Task |
Format Example |
|
Request return availability using same date with new time |
1R(time) |
|
Request return availability, add or subtract specified |
1R‡(number of days) |
|
Request return availability for specified number of days, change
departure time No more than 30 days forward or backward may be
requested in any single entry |
1R‡(number of days)* |
|
Request return availability for specific date, same |
1R(day of month) |
|
Request return availability for specific date, different |
1R(new month) |
|
Request return availability for specific date and time |
1R(return date)(departure time) |
Sell From City Pair availability
After availability is displayed, the next step is to sell the desired seats
to create a Passenger Name Record (PNR). The Sabre system offers
different ways to request airline seats from participating carriers.
Selling Options
|
Task |
Format Example |
|
Sell specified number of seats, in a requested class |
0(number of seats)(class of |
|
Sell specified number of seats, in a requested class |
0(number of seats)(class of |
|
Long sell entry |
0(carrier)(flight number)(class)(date) |
Example: Sold Segment
01Y1«
1 DL 742 Y 15OCT F ATLBOS SS1 902ª 1123ª /DCDL /E
Display Entries
|
Task |
Format Example |
|
Display the entire PNR. |
*A |
|
Display the entire Itinerary. |
*I |
|
Display only the Itinerary Air segments |
*IA |
Ignore Passenger Name Record (PNR)
|
Task |
Format Example |
|
Using this format ignores any PNR information |
I |
Waitlisting A Flight Segment
Agents use formats to request waitlisted space on a specific flight from an availability display using the short sell entry when a flight is showing zero (0) seats available in the booking class they desire.|
Task |
Format Example |
|
Waitlist a seat from specified CPA line |
0(number of seats)(class of service) |
|
Waitlist a seat from specified CPA line |
0(number of seats)(class of service) |
|
Waitlist different classes of service from |
0(number of seats)(class of service) |
Display Air Schedules
Travel agents use formats to display flight schedules regardless of availability. The entries to display air schedules are identical to CPA entries, except the letter “S” is used instead of the number “1”.|
Task |
Format Example |
|
Display flight schedules |
S(schedule date)(departure city)(arrival city) |
|
Display schedules and specify airline |
S(schedule date)(departure city)(arrival |
|
Display schedules with a specific booking |
S(schedule date)(departure city)(arrival |
|
Display schedules and specify a |
S(schedule date)(departure city)(arrival |
|
Display return schedules for specified |
SR‡(number of days) |
|
Display return schedules with new date |
SR(new schedule date) |
|
Display return schedules same date |
SR |
|
Redisplay schedule |
S* |
Schedules can be accessed up to 331 days from today. However, basic booking
request carriers only display schedules for dates up to 180 days from today,
or up to the sales date limit set by the carrier, whichever occurs
first.
Flight Information
Additional information regarding flight schedules and itineraries can be
retrieved with
various formats. You can request flight verification on a specific flight
number with
departure date, from a city pair availability display, or from a booked
itinerary.
The following formats verify flight information and display the details
pertaining to:
• departure and arrival time and dates
• enroute stops
• meal service
• equipment
• elapsed flying time
• mileage
• smoking/non-smoking flights
• shared carrier name, if applicable
Verify Flight Information from City Pair Availability (CPA)
|
Task |
Format Example |
|
Verify flight information from availability segment |
VA*(segment number) |
|
Verify flight information from a range of availability |
VA*(segment numbers) |
|
Verify flight information for specific availability segments
|
VA*(segment number)/ (segment |
|
Verify flight information with carrier code, flight number, |
V*(airline code)(flight |
Example: Verify Flight Information from CPA
VA*2«
08AUG FLT SEGMENT DPTR ARVL MEALS EQP ELPD MILES SM
2 QF 8 LAX SYD 1300 2040 LD/LD/LD 744 14.40 7509 N
DEP-TOM BRADLEY INTL TERM ARR-INTERNATIONAL TERMINAL
Flight Information Explanation
|
Header |
Description |
|
FLT |
Carrier code and flight number |
|
SEGMENT |
Departure and arrival cities for the segment |
|
DPTR |
Flight’s departure time |
|
ARVL |
Flight’s arrival time |
|
MEALS |
Meal types served in each class or cabin. |
|
EQP |
Type of aircraft for flight |
|
ELPD |
Duration of the flight in hours and minutes |
|
MILES |
Number of miles for this flight |
|
SM or SMD |
Smoking indicator |
Verify Flight Information from PNR Itinerary
|
Task |
Format Example |
|
Verify flight information from a booked itinerary |
VI* |
|
Verify flight information for a specific segment |
VI*(segment number) |
|
Verify flight information for a range of flight |
VI*(segment number)- |
|
Verify flight information for non-consecutive flight |
VI*(segment number)/ |
Example: Itinerary
*I
1 AA1777B 29APR Q ATLSJU SS2 751A 109P /DCAA
2 AA 508B 07MAY F*SJUMIA SS2 930A 1220P /DCAA
3 AA2120B 07MAY F MIAATL*SS2 130P 327P /DCAA
.png)
DISPLAY FLIGHT INFORMATION (FLIFO)
These formats display actual operational information about a specific flight
within 24 hours of departure. The different participating carriers in this
program have different requirements about the entry format.
|
Task |
Format Example |
|
Display flight information for today |
2(airline code)(flight number) |
|
Display flight information for future date |
2(airline code)(flight number)/(date of departure) |
|
Display flight information with required |
2(airline code)(flight number)/(date)(boarding point)(off |
Connectivity Tags
Connectivity tags indicate the method of communication between Sabre and an airline.These codes appear at the end of the line in CPA displays and itinerary segments. You will
receive more detailed coverage on this topic later.
|
Indicator |
Task |
Format Example |
|
/E |
Electronic Ticketing |
Indicates Electronic Ticketing is available for this
flight/carrier. |
|
/DC(carrier code) |
Direct Connect Sell |
The agent can send and receive data seamlessly from the airline’s
reservation system while they remain in the Sabre system. |
|
/DCA(carrier code) |
Direct Connect |
The agent receives true availability in the Sabre system
city pair availability display as if they were in that airline’s
reservation system. |
|
/AB(carrier code) |
Answerback |
Answerback
functionality means after the agent makes the booking, the airline
returns the record locator to the Sabre system via normal
teletype transmission. |
|
/TA |
Multi Access or Direct |
Direct Access
provides the agent access to and viewership of the airline’s
reservation system while they remain in the Sabre system when
they sell a segment. Multi Access allows the agent to leave
the Sabre system and work in the airline’s reservation
system. |
|
/AT |
Multi Access or Direct |
The airline is in Direct Access connectivity and offers the
Answerback feature. The segment sold from the
Direct Access display on an Answerback participant is
considered guaranteed. |
|
/CL |
Claim It |
The agent has claimed a record booked with a participating airline.
An image of that reservation is moved into Sabre and the
itinerary segments show a CLXX tag. XX is the two-letter airline
code. |
Insert and Cancel Segments
Air and auxiliary itinerary segments can be moved or reordered after a specified segment. These entries can be made to an itinerary before or after a PNR has been ended. The itinerary remains in the insert mode until after either a *A or *IA entry is made.
Insert/Reorder Segments
|
Task |
Format Example |
|
Insert after segment, and sell from |
/(insert after segment number)/(sell entry) |
|
Insert after segment 2, and insert segment 4 |
/(segment number to insert after)/ |
|
Insert before segment 1 and sell from CPA |
/0/(sell entry) |
|
Insert before segment 1, a different itinerary |
/0/(segment number) |
Insert ARNK (Arrival Not Known)
|
Task |
Format Example |
|
Insert an ARNK after segment 2 |
/(insert after segment number)/0A |
|
Auto insert of an ARNK whenever applicable |
0AA |
Cancel PNR Itinerary Segments
Sabre transmits the cancel message to a carrier when you end transaction.|
Task |
Format Example |
|
Cancel all itinerary segments |
XI |
|
Cancel a specific itinerary segment |
X (segment number) |
|
Cancel multiple itinerary segments |
X(segment number)/(segment number) |
MARRIED SEGMENTS
Carriers have the ability to control inventory by treating two or more segments as a singleunit. Married segments are segments that a carrier returns to an itinerary as joined. The
symbol * precedes the outbound city pair and follows the return city pair to indicate that the
segments are married.
3 AM 574Y15MAR W*CUNMEX HK1 210P 425P/DCAM*IMHCK5
4 AM 466Y 15MAR W MEXGDL*HK1 630P 735P/DCAM*IMHCK5
Any action taken on one segment in a married connection must be taken on
all segments.
This restriction applies to changing the class of service or canceling any
of the segments. To cancel one segment, you must cancel the entire married
connection in one entry. For example: If segment 3 and 4 are married, you
cannot type X3 (enter), then X4 (enter). You must use X3/4 to cancel both
segments at the same time.
If the user attempts to sell/insert an air segment between married segments,
an error response displays
‡UNABLE TO INSERT AIR SEGMENT BETWEEN A MARRIED CONNECTION‡
Example: A three segment married connection
1 AM 475Y 5DEC S*IAHCUN HK1 930A 1130A/DCAM*KVGQX3
2 AM 17Y 5DEC S CUNMEX HK1 230P 445P/DCAM*KVGQX3
3 AM 19Y 5DEC S MEXLAX*HK1 600P 755P/DCAM*KVGQX3
CANCEL and REBOOK SEGMENTS
If you cancel more than one segment and use separate entries, cancel the highest numbered segment first. The system internally re-numbers the itinerary once you make the itinerary display entry, *I.
|
Task |
Format Example |
|
Cancel segment and sell from city pair |
X(segment number)‡(sell entry) |
|
Cancel and rebook flight and class for new |
X(segment selection)‡00(new date) |
|
Cancel and rebook new segment by flight |
X(segment number)‡0(long sell entry) |
If the requested flight is not available, the system cancels the existing
segment and redisplays city pair availability for the requested date.
Create and Modify Passenger Name Records
PNR is an acronym which stands for Passenger Name Record. It contains all
the information necessary for an agency’s client reservation. Agencies
include various optional and mandatory components when creating PNRs. Some
carriers have restrictions and limitations to the formats and characters
they accept. Therefore, it is important to use standard formats to insure
information is properly transmitted. A passenger reservation cannot be
completed without the following:
Five Mandatory Components
The PRINT acronym is helpful to recall all the mandatory PNR components.
There is no
required order for entering these fields.
• Phone
• Received from
• Itinerary
• Name
• Ticketing
Example
*A
1.2JONES/ALAN/DORIS
1 DL1402F 24JUN J SNAATL HK2 850A 403P /DCDL*XAHFH7 /E
2 DL1445F 30JUN F ATLSNA HK2 605P 755P /DCDL*XAHFH7 /E
TKT/TIME LIMIT
1.TAW11JUN/
PHONES
1.SNA715-955-6610-A
RECEIVED FROM - DORIS
C252.C252*ALD 1227/21APR06 RTSMSC H B M
The last line of a PNR is called the signature line. It appears when a
passenger record is ended. The signature line includes the following
information:
C252.C252*ALD 1227/21APR06 RTSMSC H B M
|
Component |
Description |
|
C252.C252 |
Pseudo City Code. Pseudo City Code |
|
* |
Duty Code of agent who created PNR |
|
A |
Agency |
|
LD |
Agent Sign |
|
1227/21APR06 |
Time/Date PNR was created- military CST time |
|
RTSMSC |
Record Locator |
|
H |
PNR contains History – changes made after the original end
transaction. |
|
B |
PNR contains Pre-Reserved Seats |
|
M |
PNR contains Direct Connect Marketing Messages |
Note: A PNR signature line will only include H, B, or M if the record
contains history,
pre-reserved seats, or direct connect marketing messages.
Itinerary
You have learned how to display availability and sell air segments which
begins the creation of a PNR. The itinerary field is the area that holds all
of the passenger’s travel information In addition to air travel, a PNR may have auxiliary segments such as:
• Car • Hotel • Rail
• Tour • Cruise • Insurance
• Prepaid Ticket (PTA) • Miscellaneous Charge Order (MCO)
• Other (OTH) segment types such as agency service fees or retention
segments
Note: You will learn about all of these auxiliary segments in later
lessons.
Name Field
The name field (-) holds the passengers name(s). The number of names must
match the number of seats booked in the itinerary.
Some agencies add reference numbers or codes to the name field for
accounting or identification purposes. The reference number is also referred
to as a MAN number, and is not transmitted to the airline. Any combination
of up to 29 characters with letters, numbers, comma, period (.), dash (-),
slash (/), or display (*) are acceptable.
|
Task |
Format Example |
|
Enter a passenger name |
-(last name)/(first name) (title) |
|
Enter names for more than one person with the same last name |
-(number in party with same last name) |
|
Change a single passenger name field |
-(name field number)(last name)/(first name) (title) |
|
Change a multiple passenger name |
-(name field number)(number in party) |
|
Delete a name field (applicable when there is only one name
field) |
- |
|
Delete a specific name field |
-(name field number) |
|
Delete a name from a multiple |
-(name field number) |
|
Display the name field only |
*N |
|
Add name with reference number |
-(last name)/(first name)*(reference number) |
|
Add or change name reference number when name is already in the
PNR |
-name number*(reference number) |
|
Delete name reference number |
-name number* |
Example: Name Association
Entry: -3BAKER/RAY MR/MARIE MRS/STEVE MSTR
Response after redisplay:
1.3BAKER/RAY MR/MARIE MRS/STEVE MSTR
Name association: 1.1 1.2 1.3
Optional Titles:
|
Abbreviation |
Title |
Definition |
|
DR |
Doctor |
Person holding the degree of doctor |
|
JR |
Junior |
Son having the same given name as the father |
|
SR |
Senior |
Father having the same name as the son |
|
II |
the Second |
Next after the first; a son having the same name as the father. |
|
III |
the Third |
Next after the second; son having the same name as the |
|
LT |
Lieutenant |
Officer holding a commissioned military or police force rank |
|
CAPT |
Captain |
Officer holding a commissioned military or police force rank |
|
SR |
Sister |
Member of a religious order of women |
|
BR |
Brother |
Member of a religious order of men |
|
FR |
Father |
A priest or clergyman |
|
MR |
Mister |
Male of any age |
|
REV |
Reverend |
Clergy member or spiritual leader |
|
MLLE |
Mademoiselle |
Female child or unmarried woman in a French-speaking area |
|
MISS |
Mistress |
Female child, age 2 to 11 years |
|
MS |
-neutral- |
Married or unmarried female, any age |
|
MRS |
Mistress |
Married woman |
|
MSTR |
Master |
Male child, age 2 to 11years. |
Phone Field
The phone field (9) stores all phones numbers in the PNR. It is recommended
that travel
agents use industry standard phone field formats. If there are multiple
phone contacts, the agency phone number should be listed first. When notes,
remarks, and non-standard characters such as * , ‡ / # are included in the
phone field, this may cause slow responses teletype rejects from some
carriers.
|
Task |
Format Example |
|
Enter the phone field |
9(area code)-(prefix)-(number)-(identifier) |
|
Enter the phone field with an |
9(area code)-(prefix)-(number)X (extension)-(identifier) |
|
Change a phone number |
9(item number)(new phone number)-(identifier) |
|
Delete a phone number |
9(item number) |
|
Display the phone field only |
*P9 |
|
Identifiers: A = Agency B = Business H = Home |
Ticketing Field
The ticketing field (7) allows information to be entered to store a date and
queue information prior to ticketing, depending on the agency needs. After
ticketing, this field is automatically updated with ticket numbers.
|
Task |
Format Example |
|
Automatically place PNR on Queue 9 (ticketing queue) on a specified
date |
7TAW(ticket date)/ |
|
Automatically place PNR on a specified date and a personal
queue |
7TAW(ticket date)/ |
|
Place PNR on Queue 9 (ticketing queue) immediately |
7TAW/ |
|
Shows a PNR as ticketed. Used for immediate ticketing (i.e.
handwritten tickets, instant purchase, walk-ins). PNR will not queue
place to ticketing queue |
7T-A or 7T-text |
|
Change a ticketing date |
7TAW(new date) / |
|
Future ticketing time limit specifying a downline city, carrier,
time, and date For all Airlines except AA |
8(downline city)-(carrier |
|
Add ticketing time limit for American Airlines, assume today’s
date |
8(time) |
|
Display the ticketing field only |
*T |
Received From Field
The Received from Field (6) is used to identify the person who made or
requested the change to the PNR.
|
Task |
Format Example |
|
Enter the received from field Note: 6P is commonly used to indicate
received from Passenger |
6(name) |
|
Change received from field |
6(name) |
|
Display the received from field and signature line of a PNR
|
*P6 |
Whether you create or change an existing PNR, you must always either end or
ignore your transaction. When you End, you want to save the transaction.
When you Ignore, you want to disregard the transaction.
End Transaction
|
Task |
Format Example |
|
End the PNR and store it in the Sabre database |
E |
|
End and redisplay the PNR |
ER |
|
End the PNR and send an email message to the client about the
itinerary viewable on the Virtually There website. The email address
must be in the PNR email address field. |
EM |
|
End PNR and send e-invoice advising an electronic invoice is |
EMI |
|
End PNR and send electronic ticket notification to all email |
EMT |
Ignore PNR
These formats are used to ignore a PNR and remove any changes made since the last time a record was ended.|
Task |
Format Example |
|
Ignore entries entered to input information into a PNR. This clears
the screen and returns a previously ended PNR to the database
without changes. |
I |
|
Ignore and redisplay the PNR. Used to ignore changes you do not
want to save. |
IR |
Optional PNR Data
A PNR normally includes various optional fields which provide important
details useful to the travel agency and their client.
Remarks Field
The remarks field (5) is where all PNR remarks are stored. It is used to input customer and agency information, the form of payment, and accounting data. Different formats are used depending on the type of remarks being added to the PNR.
Note:
When more than one form of payment field has been entered in the remarks
field, thesystem uses only the first 5- field.
|
Task |
Format Example |
|
Store CHECK form of payment in the PNR |
5-CHECK |
|
Store CASH form of payment in the PNR |
5-CASH |
|
Task |
Format Example |
|
Store credit card form of payment. The credit card number on the
passenger receipt will be masked, except for the last four digits.
Note: If the * is not included in the form of payment entry, the
system does not check for credit approval at the time of ticketing.
The system does not permit ticketing for amounts less than $1.00
USD. |
5-*(two-letter credit card code) |
|
Store credit card form of payment in the PNR, but suppress the
credit card information from printing on the invoice/itinerary |
5-*(two-letter credit card code) |
|
Change the form of payment in a remarks line |
5(item number)(new text) |
|
Delete a remarks line |
5(item number) |
|
Add general information that is not transmitted to the airlines |
5(free text) |
|
Add historical remarks. The information is |
5H-(free text) |
|
Add coded remarks. This information will not print on the
invoice/itinerary. |
5(alpha code)‡(free text) |
|
Add segment associated invoice remarks. This information will print
on the invoice. |
5.S(segment number)(space)(text) |
|
Add segment associated itinerary remarks. |
5‡S(segment number)(space)(text) |
|
Print remarks on itineraries |
5‡(remarks) |
|
Print remarks on Invoices |
5.(remarks) |
|
Display the Form of Payment field only |
*- |
|
Display only passenger data – remarks |
*P5 |
|
Display alpha coded remarks |
*(code letter)‡ |
Address Fields
|
Task |
Format Example |
Description |
|
Client’s |
5/(client's name) |
Maximum of six lines of text with up to 50 characters per line and
each line must begin with 5/ |
|
Delivery |
5DL-(address information) |
Maximum of six lines of text with a maximum of 39 characters and
each line must begin with a 5DL |
|
Agency’s |
W-(agency name)‡(street address)‡(city), |
Maximum of six lines of text with a maximum of 50 characters and
each line must begin with a W |
|
Agency’s |
W-(agency name)‡(street address)‡(city), (state) (zip) |
For example, if the agent typed W ABC TRAVEL‡123 MAIN ST in the
previous entry, the insert after line number is 2. The ABC TRAVEL
occupies line 1 of the address field. The ‡ separates the data 123
MAIN ST that occupies the second line of |
|
Insert agency |
W-(address line number to insert after)/ (city/state or country/zip
or postal code) |
See above example |
|
Delete entire |
W-¤
|
Delete the entire Agency Address Field |
|
Delete |
W-(line number)¤ |
Delete specific address line for the Agency Address Field |
|
Change line |
W-(line number)¤(new address |
Change a specific line of the Agency Address Field |
|
Display Entry |
*/
|
Display Clients Address Field |
|
Display Entry |
*DL-
|
Display Delivery Address Field |
|
Display Entry |
*PAD
|
Display Agency Address Field |
Note: All of the above address fields are optional fields. Only ONE Agency
Address
Field can be input in a PNR.
Passenger E-Mail Address Field
An e-mail address can be added or deleted to a PNR in the PE field. When you
change or delete a passenger name from your PNR, the e-mail address
associated with that name is also changed or deleted. The system permits a
maximum of 999 PE‡ fields in a PNR. A cross of lorraine (‡) after the PE
code indicates the start of the e-mail address. A second cross of lorraine
(‡) at the end of the e-mail address is required. The e-mail address must
have one at sign ( @ ) between the cross of lorraines (‡). The e-mail
address field must be completed before using one of the EM commands which
sends the e-mail to the specified email addresses in the PNR.
|
Task |
Format Example |
|
Enter the passenger e-mail field |
PE‡(e-mail address)‡ |
|
Change the passenger e-mail field |
PE(line number)¤‡(new e-mail information)‡ |
|
Delete e-mail address field from the PE field |
PE(line number)¤ |
|
Delete multiple e-mail address fields from the PE Field |
PE(line number),(line number), (line |
|
Creates a custom subject line for the e-mail message. Agents can
include one subject line with free text. The free text is limited to
65 characters. |
5V‡SL-(free text) |
|
Adds free text in e-mail message |
5V‡EM-(free text) |
|
Display all passenger e-mail address fields in a PNR |
*PE |
Frequent Traveler Numbers
These formats are used to store a passenger’s frequent flyer number in a
PNR. A message is transmitted to a participating carrier to give passengers
mileage credit for the bookings made in the Sabre system.
A separate frequent flyer entry must be made for each name and airline. The
name field in the PNR must match the carrier’s frequent flyer card name to
ensure mileage credit. The system generates a message to send this
information to the carrier.
|
Task |
Format Example |
|
Transmit frequent flyer number |
FF(airline code)(number)-(name field number) |
|
Transmit frequent flyer number of one |
FF(airline code)(number)/(airline code)-(namefield number) |
|
Delete a frequent flyer number |
FF(frequent flyer line number)¤ |
|
Delete a range of frequent flyer numbers |
FF(first frequent flyer line number)-(last frequent |
|
Delete specific frequent flyer numbers |
FF(frequent flyer line number),(frequent flyer line |
|
Delete all frequent flyer numbers |
FF¤ALL |
|
Modify frequent flyer information |
(FF line number)¤(carrier code)(frequent traveler |
|
Display frequent flyer field |
*FF |
OSI (Other Service Information)
Agencies use Other Supplementary Information (OSI) messages when they need
to send information to the carrier that does not require action or a reply
by the carrier. These are lowpriority messages usually used for information
purpose only. OSI messages are sent to carriers, however,
Sabre cannot guarantee the carrier will process the message. This
will be discussed in more detail later.
|
Task |
Format Example |
|
Transmits a message to a carrier |
3OSI (airline code) (free text) |
|
Transmits information to a particular |
3OSI (airline code) (free text)-(name field number) |
|
Transmits information to American |
4OSI (free text) |
|
Task |
Format Example |
|
Transmits information to AA for a specific passenger name |
4OSI (free text)-(name number) |
|
Delete a single GFAX field |
3(line number)¤ |
|
Delete multiple GFAX fields |
3(line number),(line number)¤ |
|
Delete a range of GFAX fields |
3(line number)-(line number)¤ |
|
Delete a single AFAX field |
4(line number)¤ |
|
Delete multiple AFAX fields |
4(line number),(line number)¤ |
|
Delete a range of AFAX fields |
4(line number)-(line number)¤ |
|
Display all GFAX in the PNR |
*P3 |
|
Display all AFAX in the PNR |
*P4 |
Note: AFAX *OSI* INFORMATION - for AA ONLY
GFAX *OSI* INFORMATION - for ALL OTHER AIRLINES
A space before and after the airline code is mandatory for all airlines
except
American Airlines. The airline code should not be used for AA.
Note: Name select is not required when there is only one passenger name in
the PNR.
SSR (Special Service Request)
Agencies send Special Service Requests (SSR) messages to carriers that require action or areply. These messages require specific codes that can be found in Format Finder. The
system edits each SSR code to determine if free text is required. A slash is required when
free text information is required.
Common Types of SSR Requests
• Send Special Meal Request DU*/SPM for meal codes list
• Send Wheelchair Request (WCHS)
• Send OTHS for CC Holder to carriers (OTHS/)
• Send Group Fare Basis Code (GRPF/)
• Send Passport Info (3PSPT/) • Send Ticket Number (TKNM/)
• Send Pet in Cabin Information (PETC/) • Send Emergency Contact Information
(PCTC/)
• Send Unaccompanied Minor Information (UMNR/)
• Send Form of Identification (FOID)
SSR Formats
|
Task |
Format Example |
|
Enter frequent flyer number as FOID |
3FOID/FF(carrier code and frequent flyer number) |
|
Send SSR message for all segments |
3(SSR code)-(name number) |
|
Send SSR message for specific |
3(SSR code)(segment number)-(name number |
|
Request seat assignment with SSR |
3(seat code)(segment number)-( name number) |
|
Request assistance for passenger with |
3(assistance code)(segment number)-( name |
|
Request meal with SSR message |
3(meal code)(segment number)-( name number) |
|
Send company information (European |
3OTHS(optional segment number)/free text with |
|
Send SSR message for all segments to |
4(SSR code)-( name number) |
|
Send SSR message to American |
4(SSR code)(segment number)-(name number |
|
Delete single GFAX |
3(line number)¤ |
|
Delete multiple GFAX |
3(line number),(line number)¤ |
|
Delete range of GFAX |
3(line number)-(line number)¤ |
|
Delete singe AFAX |
4(line number)¤ |
|
Delete multiple AFAX |
4(line number),(line number)¤ |
|
Delete range of AFAX |
4(line number)-(line number)¤ |
DK Number Field in PNR
Agencies use the DK number field primarily as an account reference
identifier for billing purposes. The DK number can be letters, numbers, or a
combination. Only one DK number can be in a PNR. When another number is
entered, it replaces the previous one. An agency can require a six, seven or
10-digit
DK number.
|
Task |
Format Example |
|
Add DK number |
DK(customer number) |
Complete a PNR
After a subscriber inputs all the required (PRINT) and optional fields, they will endtransaction on the PNR. At this time Sabre sends a message to all of the carriers they sold flights on so that the carrier will create a PNR in their system. Depending on how the air itinerary segments were sold, the PNR will update with the PNR locator from the
carrier’s system.
1.2JONES/JOHN/MARY
1 BA8115N 20DEC T LGWAMS HK2 100P 310P /DCBA*2LDZP9 /E
2 AZ 117Y 10JAN T AMSMXP HK2 1155A 140P /DCAZ*LFW8HZ /E
3 AZ 116Y 12JAN Q MXPAMS HK2 305P 500P /DCAZ*LFW8HZ /E
4 BA8114V 15JAN S AMSLGW HK2 1200N 1210P /DCBA*2LDZP9 /E
TKT/TIME LIMIT
1.TAW/
PHONES
1.LON001-919-1982-A
2.LON001-831-0291-H
CUSTOMER NUMBER - 123456
ADDRESS
WORLD TRAVEL
23 KNIGHTS CROSSING
LONDON, UK 192891
GENERAL FACTS
1.OSI YY SPEAKS ONLY GERMAN
2.SSR WCHS BA NN1 LGWAMS8115N20DEC
3.SSR WCHS AZ NN1 AMSMXP0117Y10JAN
4.SSR WCHS AZ NN1 MXPAMS0116Y12JAN
5.SSR WCHS BA NN1 AMSLGW8114V15JAN
REMARKS
1.H-PASSENGER PERFERS WINDOW SEATS
2./MR JOHN JONES
3./123 CAMBRIDGE
4./LONDON, UK 191431
5.DL-MR JOHN JONES
6.DL-123 CAMBRIDGE
7.DL-LONDON, UK 191431
8.‡PENALTY APPLIES ON CHANGES AND/OR CANCELLATIONS
9..AGENCY SERVICE FRE 35.00GBP
10.C‡PREFERS ZI WIZARD NBR 2B073A
11.‡S3 CHECK IN AT LEAST ONE HOUR BEFORE DEPARTURE
12.DEPOSIT IS DUE ON MARCH 1ST
13.-*CA5419842234567898‡12/08
RECEIVED FROM - P
4K35.FSG*N3T 1109/05JUN05 KKBEEN
Display PNR
PNRs can be displayed using the following entries:|
Task |
Format Example |
|
Display PNR by last name |
*-(last name) |
|
Display PNR by passenger last name and |
*(travel date)-(last name) |
|
Display PNR by carrier, confirmed flight |
*(carrier code)(flight number)/(travel |
|
Display PNR using the Sabre record locator |
*(record locator number) |
|
Display branch office PNR by passenger name |
*-XXXX-(last name) |
Similar Name List Response
*-WALKER«
1 WALKER/JONI 03SEP-03SEP 2 WALKER/MISSY X -15MAR
3 WALKER/JOHN X -21APR
Display PNR from Similar Name List
|
Task |
Format Example |
|
Display specified PNR from similar name list |
*(number from similar name list) |
|
Redisplay similar name list |
*L |
|
Display additional names similar to previous |
*0 |
When there are additional names with a similar spelling the response below
the name list display will be: *0 FOR MORE NAMES
Divide, Increase/Reduce, and Clone PNRs
Agencies divide PNRs for a variety of reasons. When a PNR is divided, Sabre
sends a
teletype message to the applicable carrier requesting them to split the PNR
to match the
Sabre PNR. Since the message is being sent via teletype, Sabre does not
guarantee that the divide message will be processed by the carrier, which
can result in problems for both the agency and their passengers.
Divide PNR
When an agent divides a PNR with multiple passengers, the appropriate
name-associated AFAX items go into the respective split PNRs. The system
assumes that any OSI/SSR items that are not name-associated apply to all
passengers and copies them into the new PNR These items copy into the new
PNR:
• Remarks
• Air itinerary history
• Historical name associated data
These items do not copy to the new PNR:
• Phase IV ticket PNRs
• Stored Fares *WS, *WSH, PQ, *PQH
• Auxiliary segments
• Historical items that are not name associated
If unnecessary divide entries are made, this can cause the Sabre PNR(s) to
no longer match what is in the carrier’s system. The PNR locators from the
carrier may not be returned and Basic Sabre Formats and Functions Training
Guide November 2006 Divide, Increase/Reduce, and Clone PNRs 40
the subscriber may not be able to issue electronic tickets. The reasons to
divide and not
divide a PNR are listed below.
REASONS TO DIVIDE
Dividing a PNR SHOULD ONLY be done when there is an itinerary change for one or moreof the passengers that results in the party no longer traveling together on all flights.For example, when a PNR has two passengers scheduled to return on LH flight 123 for
FRA to JFK on November 15; however one of the passengers needs to remain in FRA until November 30th.
Since all air segments must match for all passengers in a PNR, the
subscriber would need to divide the PNR in order to make the necessary
changes for the passenger who is extending their stay in FRA.
This is the only valid reason to divide a PNR.
REASONS NOT TO DIVIDE
A PNR SHOULD NOT be divided when there is no itinerary change. Canceling
and
rebooking the same itinerary passengers are already holding is not a valid
reason to divide a record.
When there are multiple passengers in a PNR with different forms of payment,
the subscriber should use name select entries.
When there are multiple passengers and the subscriber wants to issue
individual tickets in order to provide separate invoice and itinerary
documents, name select and accounting line select entries should be made.
When a carrier restricts name changes for specific classes of service, the
system does not permit name changes while in the divide party mode. If a
name change is necessary, check the Name Change Restriction Table for all
carriers in the itinerary.
Note: See RK*(airline code) to view a specific airline table.
|
Task |
Format Example |
|
Divide name field number 1 from PNR |
D(name field number) |
|
Divide multiple name fields 1, 4, and 6 |
D(name field 1)*(name field 4) |
|
Divide first passenger in name field 2 |
D(name field 2.1) |
|
Divide first two persons of same surname |
D(name field)*(name field) |
|
Divide name fields 2 through 6 |
D(name field)-(name field) |
Steps to Divide
|
|
Task |
Format Example |
|
1 |
Divide specific name fields Note: Maximum 82 names in one divide
entry. See above table for name |
D(name field number) |
|
2 |
Sell air segments or Cancel and rebook |
Change the itinerary |
|
3 |
Add received from field |
6(person who made changes) |
|
4 |
File the new (child) PNR and Sabre will |
F(enter) |
|
5 |
Sell, cancel, or rebook segments in original |
Change the itinerary (if |
|
6 |
Add received from to original PNR |
6(person who made changes) |
|
7 |
End Transaction or End and Redisplay |
E, ET, or ER |
Divide Remarks
Both the new (Child) PNR and the original (Parent) PNR will update with a
historical remark
line cross referencing the other PNR.
Remark added to the parent PNR
H-SPLIT TO/091802/31OCT01 EUCMKZ 20/10
15/05 LASTNAME/FIRSTNAME
|
Item |
Description |
|
091802 |
Time of the divide |
|
31OCT01 |
Date of the divide |
|
EUCMKZ |
PNR locator of the child PNR |
|
20 |
Number in party prior to the divide |
|
10 |
Number of name fields prior to the divide |
|
15 |
Number in part after the divide |
|
5 |
Number of name fields after the divide |
|
LASTNAME/FIRSTNAME |
First 12 characters of the primary name in the parent PNR. May also
be the name of a group if a /B or /C is present |
Remark added to the child PNR
H-SPLIT FR/091802/31OCT01 EUCXYZ 20/10
05/05 LASTNAME/FIRSTNAME
|
Item |
Description |
|
091802 |
Time of the divide |
|
31OCT01 |
Date of the divide |
|
EUCXYZ |
PNR locator of the parent PNR |
|
20 |
Number in party prior to the divide |
|
10 |
Number of name fields prior to the divide |
|
15 |
Number in part after the divide |
|
5 |
Number of name fields after the divide |
|
LASTNAME/FIRSTNAME |
First 12 characters of the primary name in the child PNR. |
Increase Number in Party
These formats can be used during original creation of a PNR before it is ended. Once a PNR has been ended the number of passengers in the PNR can never increase. After ending transaction, a new PNR must be created in order to increase the number of passengers.
|
Task |
Format Example |
|
Increase number of passengers on all |
,(new number of passengers) |
|
Increase number of passengers on specific segment or range of
segments |
,(new number of passengers) |
Reduce Number in Party
These formats reduce the number of passengers in a PNR.|
|
Task |
Format Example |
|
1 |
Cancel all seat assignments |
4GXALL |
|
2 |
Delete all name fields of passengers no longer required in the
PNR |
-(name field)¤ |
|
3 |
Reduce number of passengers |
,(new number in party) |
|
4 |
Receive PNR |
6P |
|
5 |
End Transaction or End and |
E, ET, ER |
Note: An agent might attempt to reduce the number of passengers in a PNR
containing
segments on which the carrier has restricted name changes. If they remove a
name
field, then try to add the name field back into the PNR as though it were a
new
name, the following warning message displays:
NAME CHANGE NOT ALLOWED FOR RESTRICTED FARE CLASSES
If this response is received, they must ignore their PNR by typing (IR) and
begin again. The agent must cancel only the name number of the person or
persons they are removing from the PNR.
Clone PNR Data
Sometimes agencies need to clone a PNR in order to create multiple PNRs for
the exact same itinerary. Cloning a PNR saves them time by not having to
display and sell flights over and over again. Here are some rules to keep in
mind when discussing the option of cloning a PNR:
• An agent can use these formats to clone only the itinerary from an
existing PNR into a
new PNR.
• The system resells the space in the new PNR. It clones no other data from
the original
PNR.
• They can select segment numbers or types that should not be cloned.
• They can select only one segment type per entry. They cannot combine
segment type
with segment number in one entry.
• They must use the end and clone (EC) entries when they have made
changes to the
original PNR and not ended transaction prior to the clone request.
• They must use the ignore and clone (IC) entries if no changes were
made to the original PNR.
An agent CANNOT clone a PNR:
• If they are on queue
• In the middle of completing a divide party request
• In combination with a request for an Invoice/Itinerary
Steps to clone
|
Task |
Format Example |
|
Ignore and clone all itinerary segments |
IC |
|
Ignore and clone itinerary and passenger data fields, or specified
passenger data fields |
ICA(Passenger Data Field Code) |
|
Task |
Format Example |
|
Ignore transaction/clone specified passenger data fields/exclude
itinerary |
ICAPD,XI |
|
Ignore/clone itinerary for name 1.1 and add all phone fields |
ICAN1.1,AP9 |
|
End and clone all itinerary segments |
EC |
|
End and clone itinerary and passenger data fields or specified
passenger data fields. |
ECA(Passenger Data Field Code) |
|
End transaction/clone specified passenger data fields/exclude
itinerary |
ECAPD,XI |
The system does not clone the following items:
• Form of Payment • Historical Remarks
• Agency Address • Divide Party
• Pre-Reserved Seats • Pre-Paid Data
• Accounting Lines • Received From field
• OSI/SSR • PNR locator
• Ticketing field on a ticketed PNR
Sabre Replay
Sabre Replay is a Windows function that saves keystrokes and helps repeat previous entries.Either individual or a series of entries can be repeated to prevent the need to retype.
In order to use this function, Sabre for Windows and My Sabre users can:
• Use keyboard functions, or
• Click on Tools on the menu bar, then select the Sabre Replay option
Depending on the Windows version, 50 to 350 previous entries can be
recalled. This is an extremely helpful function to use while assisting
subscribers who incorrectly input formats and must reenter. When the
keyboard is used to replay a single entry, changes can be made to the format
prior to pressing enter. When the “simultaneous changes” response is
received in a PNR, it can be ignored and the entries can be replayed.
Sabre Keyboard Function
|
Task |
Sabre Keys |
|
Use this keyboard function to replay your previous entries – moving
backward |
Press -ALT- + -up arrow- () |
|
Use this keyboard function to replay your previous entries – moving
forward |
Press -ALT- + -down arrow- ( ) |
Common Calls and Error Responses
You will receive a variety of calls from subscribers related to basic formats and functions.Format Finder and Rapid Results will be your primary references to locate information and
formats to assist your customers. Examples of common calls are listed below.
|
Type of Call |
Steps to resolve |
|
You receive a call from a |
1. Place the caller on monitor |
|
A subscriber calls asking for |
1. Confirm your understanding of the request and refer them to
their account team. |
Basic Sabre Formats and Functions Training Guide November 2006 Common Calls
and Error Responses 48
|
You receive a call from a travel |
1. Locate the Format Finder page to find the proper format. Check
Sabre Atlas topics or use search keywords: military base or 10
closest. |
|
A subscriber calls to report a |
1. Apologize for the situation and advise you will make a report to
have the correct information verified and updated.
4. Ask your customer to please stay on the line while you quickly
complete the report. Note: You will learn reporting procedures
later. |
|
A subscriber tells you they |
1. Place the caller on monitor, and request the caller display the
PNR. |
Basic Sabre Formats and Functions Training Guide November 2006 Additional
References 49
|
A travel agent calls for |
1. Request the record locator. |
Additional References
The table below contains references you can review for additional information and formats on the topics contained in this training guide.Helpdesk and Subscriber References
|
Reference |
How to Find It |
|
Format Finder
|
From the Format Finder Home page choose from the following
topics: |
|
Rapid Results
|
From the Rapid Results Home page choose from the following
topics: |
|
Sabre |
• DU*/MLS |
|
Agency |
You can find Format quick references on the Web at
http://eservices.sabre.com/ |
Basic Sabre Formats and Functions Training Guide November 2006 Additional
References 50
|
Personal |
You can find additional training and references in
Personal Trainer education |