A complete guide to the RP command in Amadeus โ how to change the responsible office and related office assignments for a PNR, including ticketing, queuing, and option element offices.
Every PNR in Amadeus is owned by a responsible office โ the office that controls the booking, handles ticketing, and receives the associated reporting. When a booking is transferred between branches, taken over by a different department, or reassigned as part of a corporate restructure, the responsible office must be updated. The RP command is the entry that handles this. It allows you to change the responsible office, as well as the option element, ticketing, and queuing offices, so that the PNR is correctly assigned to the right location or department. This guide explains what RP does, the syntax for each scenario, and when it should be used.
What Does the RP Command Do?
RP is the Amadeus GDS command used to change the responsible office and related office assignments for a PNR.
Category: PNR Management.
It allows you to change the responsible office, as well as the option element, ticketing, and queuing offices.
This is important because the responsible office determines which office profile settings apply, where the ticket is reported, and which queue receives the booking for processing. Changing it incorrectly can result in tickets being reported to the wrong branch or queues being missed entirely.
Change Responsible and Option Element Office
To change the responsible office and the option element office together:
RP/MUCLH0100/OPThis changes the responsible office and the option element office to MUCLH0100. The /OP indicator specifies that the option element office should also be updated along with the responsible office.
Change All Office Assignments
To update every office assignment in one entry:
RP/MUCLH0100/ALLThis changes the responsible office, ticketing office, queuing office, and option element office โ all in a single command. Use this when a PNR is being fully transferred to a new office and every associated assignment should follow.
Change Responsible Office for an AXR-Linked PNR
To change the responsible office for only one AXR-linked PNR:
RPS/MADAF0200The RPS variation changes the responsible office for a single PNR that is linked through AXR, without affecting other linked records. This is useful when only one booking in a linked group needs to be reassigned.
When to Use RP
Use RP when you need to transfer or modify the office responsible for a PNR and, when required, update its related ticketing, queuing, or option element office. Typical scenarios include:
- Transferring a booking from one branch office to another.
- Reassigning a PNR to a different department or team within the same agency.
- Correcting a PNR that was created under the wrong responsible office.
- Moving bookings after an office restructure, merger, or closure.
- Handling AXR-linked PNRs where only one record needs reassignment.
- Updating the ticketing or queuing office so that the booking is processed by the correct team.
How RP Fits Into Your PNR Management Workflow
A typical PNR management session using RP might look like this:
- Retrieve the PNR and confirm the responsible office needs to be changed.
- Note the target office code that should own the booking.
- Enter
RP/MUCLH0100/OPfor a partial update, orRP/MUCLH0100/ALLfor a full update. - For AXR-linked PNRs, use
RPS/MADAF0200to change only one record. - End the transaction to save the change.
- Display the PNR to confirm the new responsible office and related assignments.
- Verify that the PNR appears in the correct office queue.
Important: The responsible office controls which office profile settings apply to the PNR, including commission control, ticketing rules, and queue assignments. Changing it to the wrong office can cause tickets to be reported incorrectly or bookings to be missed by the processing team.
Always confirm the target office code before running RP, and check that the PNR appears in the correct queue after the change.
How RP Relates to Other PNR Management Commands
- RP โ changes the responsible office and related office assignments.
- RPS โ changes the responsible office for a single AXR-linked PNR.
- QE / QER โ places a PNR on a queue or adds it to another queue.
- RTQ โ displays all queues containing the current PNR.
- QS / QSB โ start processing or browse a specific queue.
- QR โ removes all PNRs or messages from a queue.
Frequently Asked Questions
What does RP/MUCLH0100/ALL do?
It changes the responsible office, ticketing office, queuing office, and option element office to MUCLH0100 in a single entry.
What is the difference between RP and RPS?
RP changes the responsible office and related assignments for the PNR. RPS changes the responsible office for only one AXR-linked PNR.
What does the /OP indicator mean in RP?
It specifies that the option element office should also be updated along with the responsible office.
Conclusion
The RP command allows you to change the responsible office and related office assignments for a PNR in Amadeus. Use RP/MUCLH0100/OP to update the responsible and option element offices, RP/MUCLH0100/ALL to change every related assignment at once, and RPS/MADAF0200 to change the responsible office for a single AXR-linked PNR. Because the responsible office controls profile settings, ticketing rules, and queue assignments, always confirm the target office code before running RP. Paired with QE, QER, RTQ, and QS, the RP command ensures every PNR is owned by the right office and processed by the right team.
