When
Something in an element is wrong (a remark text, the TK date, the passenger it belongs to), or the flights are listed in the wrong order.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | RT | Redisplays the PNR with current element numbers. | Numbers shift after every change. |
| 2 | 5/NEW REMARK TEXT | Replaces the text of element 5. | Most elements change this way: line number, slash, new value. |
| 3 | 5/P2,3 | Associates element 5 with passengers 2 and 3. | Correct who it belongs to. |
| 4 | 4/P · 4/S | Removes the passenger · the segment association of element 4. | Make it apply to all. |
| 5 | 8/10JUL | Changes the date of the TK element on line 8. | Move the ticketing reminder. |
| 6 | 4/2 | Changes the number of seats in air segment 4 to 2. | One passenger fewer or more — the airline must accept it. |
| 7 | RS 2,5-8 | Rearranges the segments in this order. | Chronological itinerary for the client. |
| 8 | RF + name, ER | Saves. |
Check it worked
RT shows the new value on the same line.
Traps
- Changing a flight (date, class, flight number) is not done with
4/…— useSBrebooking (Rebooking a flight to another date, class or flight number (SB)). - On a ticketed PNR, changes to names, flights or passenger types break the link with the ticket — see Void, refund, revalidation or reissue — which one this case needs.