A complete guide to the EF command in Amadeus โ how to end the transaction and file a split PNR after separating passengers from the original booking.
Splitting a PNR is a two-step process. First, the passenger is separated from the original booking using the SP entry. Then the transaction must be closed and the newly created split PNR must be filed so it becomes a permanent record with its own record locator. The EF command is the Amadeus entry that handles this second step. Without EF, the split is not saved, and the new PNR does not exist as a retrievable booking. This guide explains what EF does, the correct sequence with SP, and when it should be used.
What Does the EF Command Do?
EF is the Amadeus GDS command used to end the transaction and file a split PNR.
Category: PNR Management.
The EF command is used after splitting passengers from a PNR. You must first use SP to split the required passenger, then use EF to end the transaction and file the split PNR.
Filing the split PNR creates a permanent record with its own record locator, separate from the original booking. Once filed, the new PNR can be retrieved, modified, priced, and ticketed independently โ while still sharing the same itinerary, unless the split also included itinerary changes.
The Correct Sequence: SP then EF
Step 1 โ Split the required passenger from the original PNR:
SP1This splits passenger 1 from the original PNR and prepares the new record.
Step 2 โ End the transaction and file the split PNR:
EFThis closes the transaction and files the newly created split PNR with its own record locator. The original PNR remains unchanged except for the removal of the passenger who has been split.
When to Use EF
Use EF when you have split one or more passengers from the original PNR and need to save and file the newly created split PNR. Typical scenarios include:
- Separating a family member into their own booking for a different itinerary.
- Splitting a group booking so some passengers travel on different dates.
- Isolating a corporate traveller from a mixed leisure booking.
- Separating passengers who require different fare treatment.
- Splitting a booking after a schedule change affects only some travellers.
- Creating a new PNR for a passenger who needs a separate ticket or invoice.
- Filing the split PNR after using SP for individual passengers.
How EF Fits Into Your PNR Management Workflow
A typical split PNR session using SP and EF might look like this:
- Retrieve the original PNR with RT and confirm which passenger needs to be split.
- Cancel any seat requests attached to the affected passenger with SX, if required by the split.
- Enter
SP1to split passenger 1 from the original PNR. - Review the newly created PNR to confirm the passengers, itinerary, and elements are correct.
- Enter
EFto end the transaction and file the split PNR. - Note the new record locator so the split PNR can be retrieved later.
- Review the change in the PNR history with RH if required.
How EF Relates to Other PNR Management Commands
- SP โ splits the passenger from the original PNR.
- EF โ ends the transaction and files the split PNR.
- IR โ ignores the current transaction and redisplays the PNR.
- IG โ ignores the current transaction without redisplaying.
- RT โ retrieves the original or split PNR.
- RH โ displays the PNR history, including the split action.
- RRA โ copies a PNR and creates an AXR-linked record, an alternative to splitting in some cases.
The distinction matters: SP prepares the split, EF files it. You must complete both steps for the split PNR to exist as a retrievable record. Compare this with IR and IG, which discard the current transaction rather than saving it.
Important: If the split PNR is not filed with EF, the split does not take effect. The passenger remains on the original PNR, and the new booking never becomes a retrievable record. Always complete the sequence with EF after using SP.
Seat requests, SSRs, and TSTs linked to the split passenger are handled according to the PNR structure. Review the new PNR carefully before entering EF โ after filing, further corrections must be made on the filed record.
Frequently Asked Questions
What does the EF command do in Amadeus?
EF ends the transaction and files a split PNR, creating a permanent record with its own record locator.
Do I need to use SP before EF?
Yes. EF is used after the passengers have been split with SP. Without SP, there is nothing to file.
What happens if I use SP but not EF?
The split is not saved. The passenger remains on the original PNR and the new booking never becomes a retrievable record.
Can I split more than one passenger at once?
Yes. The SP entry accepts multiple passenger numbers or ranges. Once all required passengers are split, enter EF to file the resulting PNR.
How do I know the split PNR was filed successfully?
After entering EF, the system confirms the transaction and provides the new record locator. Note it down and retrieve the PNR with RT to confirm the split.
Conclusion
The EF command is the filing tool for split PNRs in Amadeus. Use SP1 to split the required passenger from the original booking, then EF to end the transaction and file the newly created split PNR with its own record locator. The two commands work together โ SP prepares the split, EF saves it. Never assume the split has taken effect until EF has been entered and the new record locator is confirmed. Paired with RT to retrieve the records, RH to review the history, IR and IG to discard changes if something goes wrong, and RRA when an AXR-linked copy is more appropriate than a split, the EF command completes your PNR management toolkit and keeps every split booking accurate from start to finish.
Focus Keywords
- EF command
- Amadeus EF
- split PNR Amadeus
- SP command
- file split PNR
- end transaction split PNR
- Amadeus PNR management
- split passengers Amadeus
- RT command
- RH command
