When
The client confirmed and you will issue the ticket: the price must be stored in a TST (Transitional
Stored Ticket), which TTP issues from.
Check first
- Every passenger has a name with the right type (adult, child with date of birth, infant) —
FXPdoes not work without names. - Every segment is confirmed
HK.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | FXP | Prices the PNR in the booked classes and creates the TST(s). | One fare applies → TST created and confirmed. |
| 2 | FXT2 | If a list of fares was shown: selects the fare on line 2 and creates the TST. | Several fares in the same class. |
| 3 | TQT | Displays the TST(s). | Check fare, taxes, total, fare basis, baggage. |
| 4 | FQN1 | Rules of the stored fare. | Confirm the conditions the client accepted. |
| 5 | FXP/P1 · FXP/P2/RCH · FXP/S4 | One passenger · passenger 2 as a child · one segment. | When parts price differently. |
| 6 | RF + name, ER | Saves the PNR with the TST. | The TST is part of the PNR. |
Check it worked
The pricing answer says the TST was created; TQT lists one TST per passenger type (or per group of
passengers with the same fare).
Traps
- Price again after any change (flight, class, name type, date): the TST keeps the old price and is marked as changed (see Updating the TST itinerary and removing the PNR change flag).
- The TST price is guaranteed only until the airline changes its fare or its ticketing deadline — issue soon after pricing.
FXPwithout names answers with an error; add the names first.