A complete guide to the ERK command in Amadeus โ how to end the transaction, update advice codes, and redisplay the PNR in one entry.
Ending a transaction is usually the last step in a session โ but it is not always the only step. When a PNR contains segments that were waitlisted, requested, or added with an inactive status code, the transaction must also refresh those statuses so the airline can see the current state of the booking. The ERK command handles both tasks at once. It saves the changes made to the PNR, updates the applicable advice codes, and then redisplays the PNR. This guide explains what ERK does, its syntax, and when it should be used.
What Does the ERK Command Do?
ERK is the Amadeus GDS command used to end the transaction, change advice codes, and redisplay the PNR.
Category: PNR Management.
It saves the changes made to the PNR, updates the applicable advice codes, and then redisplays the PNR.
The three actions happen together. Unlike a simple end-of-transaction entry, ERK also triggers the update of advice codes โ the statuses that show the airline how each segment should be processed โ and then brings the PNR back on screen so you can verify the changes took effect.
Syntax
Enter the command on its own while the PNR is open:
ERK
This ends the transaction, saves the changes, updates the advice codes on the affected segments, and redisplays the PNR so you can review the result.
When to Use ERK
Use ERK when you need to end and save the transaction while changing advice codes and immediately redisplaying the PNR. Typical scenarios include:
- Confirming segments that were waitlisted, requested, or added with an inactive status code.
- Saving the PNR after correcting a segment status or advice code.
- Ending the transaction after updating segments added from availability.
- Saving changes and immediately reviewing the updated PNR without a separate retrieval.
- Refreshing segment statuses after a rebooking or schedule change.
- Confirming the PNR structure is correct after multiple segment modifications.
- Working with segments that require the status to be re-sent before the PNR can be processed.
How ERK Fits Into Your PNR Management Workflow
A typical session using ERK might look like this:
- Retrieve the PNR with RT and review the segment statuses.
- Make the required changes to the itinerary or segment advice codes.
- Enter
ERKto save the transaction, update the advice codes, and redisplay the PNR. - Verify the statuses now show the correct codes โ for example HK for confirmed segments.
- If the status is still incorrect, adjust the entry and repeat as needed.
- Review the PNR history with RH if you need to trace what was changed.
How ERK Relates to Other End-of-Transaction Commands
- ER โ ends and saves the transaction, then redisplays the PNR.
- ERK โ ends the transaction, updates advice codes, and redisplays the PNR.
- ETK โ ends the transaction, updates advice codes, and files the PNR without redisplaying.
- ET โ ends and saves the transaction without redisplaying the PNR.
- EF โ ends the transaction and files a split PNR.
- ERX โ confirms AXR cancellation and redisplays the records.
- ETX โ confirms AXR cancellation and files the records.
- IR โ ignores the current transaction and redisplays the PNR.
- IG โ ignores the current transaction without redisplaying.
The distinction matters: ER saves and redisplays; ET saves without redisplaying; ERK saves, updates advice codes, and redisplays; ETK saves, updates advice codes, and files.
Important: ERK saves the transaction permanently. If the entry is made before the PNR is ready โ for example while a segment status is still being corrected โ the changes will be saved and must be adjusted with a subsequent entry.
If you want to discard the current session instead of saving, use IR to roll back and redisplay, or IG to roll back without redisplaying.
Frequently Asked Questions
What does the ERK command do in Amadeus?
ERK ends the transaction, saves the changes, updates the applicable advice codes, and redisplays the PNR.
What is the difference between ER and ERK?
ER saves and redisplays the PNR. ERK also updates the advice codes on the affected segments before redisplaying.
What is the difference between ERK and ETK?
Both update advice codes when ending the transaction. ERK redisplays the PNR afterwards, while ETK files it without bringing it back on screen.
When would I need to update advice codes?
When segments are waitlisted, requested, or added with an inactive status code and the status must be re-sent before the PNR can be processed correctly.
Can ERK be undone?
No. ERK saves the transaction. If you need to correct something, do so with a new entry โ for example by modifying the segment or deleting an element with XE.
Conclusion
The ERK command is the combined end-of-transaction tool in Amadeus. Use ERK when you need to save the transaction, update the applicable advice codes on the affected segments, and redisplay the PNR โ all in a single entry. It is especially useful when working with segments that were waitlisted, requested, or added with an inactive status code and the status must be refreshed before the PNR can be processed. Always verify the segment statuses after entering ERK, and remember that ERK saves the transaction permanently โ it cannot be undone with IR or IG. Paired with ER for standard saves, ETK for filing without redisplay, ET for simple filing, EF for split PNRs, and RH for reviewing the history, the ERK command completes your PNR management toolkit and keeps every booking accurate from the first entry to the final save.
Focus Keywords
- ERK command
- Amadeus ERK
- end transaction advice codes
- update advice codes Amadeus
- ER command
- ETK command
- segment status update
- Amadeus PNR management
- redisplay PNR
- PNR segment status