When
Another office (a partner agency, a consolidator, an airline office) must read or change one of your office's PNRs, a PNR must be handed over, or you must take over a booking made in another system.
Steps
| # | Entry | What it does | Why |
|---|---|---|---|
| 1 | ES/GPARWL2123-R | Gives office PARWL2123 read access. | Let them look, not change. |
| 2 | ES/GPARWL2123-B | Read and write access. | Let them work on it. |
| 3 | ES/I12341234-R | Read access for an IATA number. | When you know the agency by IATA number. |
| 4 | ESX | Deletes the security element. | Stop sharing. |
| 5 | RTE · RHE | Shows the security elements · their history. | Who has access. |
| 6 | RP/MUCLH0429 | Transfers ownership to another office. | Hand the booking over for good. |
| 7 | RP/MUCLH0429/TKOP | Transfers and also moves the ticketing and queuing office. | Complete hand-over. |
| 8 | RO CO123ABC then ER | Claims a PNR created in another system. | Take responsibility for a booking made elsewhere. |
Check it worked
RTE lists the access; after RP the PNR header shows the new owner office.
Traps
- Transferring ownership is hard to undo — you may lose access yourself. Share with
ESunless a real hand-over is intended. -Nmeans no access; wildcards (***) share with many offices at once — be precise.