Split PNR Commands: Amadeus, Galileo & Sabre Guide (2026)

Q: What is the difference between splitting and cloning a PNR?

Splitting divides passengers from one PNR into separate records — the original PNR remains but with fewer passengers. Cloning duplicates the entire PNR into a new record without modifying the original. For cloning, see how to clone a PNR .

Q: How do I split a PNR in Galileo?

Use DP followed by the passenger number. For example, DP1 divides passenger 1, and DP1-3.6 divides passengers 1, 2, 3 and 6. For group bookings, use DG/10 to divide 10 unnamed passengers. Then file with F , sign with R.M , and end with ER .

Q: How do I split a PNR in Amadeus?

Use SP followed by the passenger number — for example, SP3 splits passenger 3. Then add RF P (received from), file the split PNR with ef , add RF P again on the original, and end with ET or ER .

Q: How do I split a PNR in Sabre?

Use D followed by the name field number. For example, D1 divides name field 1, D1*4*6 divides fields 1, 4 and 6, and D1.1*1.2 divides the first two passengers in name field 1. Then add 6P , file with F , add 6VICKIE , and end with E , ET or ER .

GDS PNR Management

Splitting a PNR allows travel agents to separate one or more passengers from the original booking into a new reservation using essential split PNR commands. This is essential when travellers in the same booking need different itineraries, when only some passengers are ticketing, or when a group needs to be divided for servicing.

This guide covers the exact split PNR commands for Galileo, Amadeus and Sabre, with step-by-step workflows, a master comparison table, and the pitfalls to avoid.

Quick Answer: Split PNR Commands at a Glance

🟢 Galileo

Divide one passenger — DP1
Divide multiple — DP1-3.6
Divide group — DG/10
Display divided — *DV
File new PNR — F

🔵 Amadeus

Split passenger — SP3
Add received from — RF P
File split PNR — EF
End transaction — ET or ER

🟠 Sabre

Divide name field — D1
Multiple fields — D1*4*6
First passenger in field 2 — D2.1
Add received from — 6P
File child PNR — F

If you need to duplicate a booking instead of splitting it, see our guide to how to clone a PNR in Amadeus, Galileo and Sabre. To move a record between offices, read how to transfer a PNR in Galileo, Amadeus and Sabre.

What Is a PNR Split and When Should You Use It?

A PNR split — also called a divide — separates one or more passengers from a shared booking into their own new record. The original PNR retains the remaining passengers, and the new record receives its own record locator.

Common scenarios where splitting is required:

Different return dates: Two passengers travel outbound together but return on different days.
Partial ticketing: Only some passengers are ready to issue tickets.
Group servicing: A corporate or family group needs to be divided for individual handling.
Different fare types: Passengers on different fare families cannot share a single filed fare.
Schedule disruption: One passenger needs rebooking while others remain confirmed.

Split vs Clone

Splitting divides passengers from one PNR into separate records. Cloning duplicates the entire PNR into a new record while leaving the original untouched. Use split when travellers need separate bookings; use clone when you need an identical copy. For cloning, see the PNR cloning guide.

Galileo Split PNR Commands

Travelport Galileo

Galileo uses the DP (Divide Passenger) family for splitting. The pattern is straightforward: DP followed by the passenger number or range.

Galileo Split Command Reference

Action	Command
Divide one passenger	`DP1`
Divide multiple passengers	`DP1-3.6`
Divide unnamed group passengers	`DG/10`
Divide named and unnamed passengers	`DG/5.P21-23`
Display divided booking files	`*DV`
File the new PNR	`F`
Sign and save changes	`R.M`
End transaction	`ER`

Step-by-Step: Splitting a PNR in Galileo

Retrieve the source PNR and confirm the passenger line numbers you need to divide.
Enter the divide entry: DP followed by the passenger number. For example, DP1 divides passenger 1.
For multiple passengers: use a range like DP1-3.6 to divide passengers 1, 2, 3 and 6.
For unnamed group passengers: use DG/10 to divide 10 unnamed group seats.
Display the divided records: enter *DV to review the split booking files.
File the new PNR: enter F to create the child booking.
Sign and save: add the received-from field with R.M, then end with ER.

Important

After a Galileo split, both the original and the new PNR must be signed and saved independently. Missing the R.M entry on either record can leave the booking in an incomplete state.

For a broader Galileo command refresher, see Galileo GDS guide: smart agent secrets. If you need to file the split record to a queue, read the Galileo queues guide for agents.

Amadeus Split PNR Commands

Amadeus

Amadeus uses the SP (Split Passenger) entry to separate passengers into a new record. The workflow requires adding a received-from field, filing the split PNR, then ending the transaction.

Amadeus Split Command Reference

Action	Command
Split passenger number 3	`SP3`
Add received from	`RF P`
File split PNR	`EF`
Add received from again	`RF P`
End transaction	`ET` or `ER`

Step-by-Step: Splitting a PNR in Amadeus

Retrieve the source PNR and identify the passenger line number to split.
Enter the split entry: SP3 splits passenger number 3 into a new record.
Add the received-from field: RF P (replace P with the appropriate name or initials).
File the split PNR: enter EF to create the new record.
Add received from again: enter RF P on the original PNR.
End the transaction: use ET or ER to save both records.

Pro tip

In Amadeus, the split creates an associate PNR — the two records remain linked. If you need to change a passenger name after splitting, see how to change a passenger name in a PNR.

For more Amadeus PNR management commands, browse the Amadeus commands library. If you’re new to Amadeus, start with how to create a PNR in Amadeus.

Sabre Split PNR Commands

Sabre

Sabre uses the D (Divide) family. The entry targets name fields rather than passenger numbers directly — understanding the difference is essential for correct splitting.

Sabre Split Command Reference

Action	Command
Divide name field 1	`D1`
Divide multiple name fields	`D146`
Divide first passenger in name field 2	`D2.1`
Divide passengers with same surname	`D1.1*1.2`
Divide name fields 2 through 6	`D2-6`
Add received from	`6P`
File new child PNR	`F`
Modify original PNR if needed	Rebook / Cancel Segments
Add received from again	`6VICKIE`
End transaction	`E`, `ET`, or `ER`

Step-by-Step: Splitting a PNR in Sabre

Retrieve the source PNR and review the name field structure. Sabre uses name fields, which may contain multiple passengers with the same surname.
Enter the divide entry: D1 divides name field 1. Use D1.1*1.2 to divide the first two passengers in name field 1.
For multiple name fields: use D1*4*6 to divide name fields 1, 4 and 6.
Add received from: enter 6P (replace P with the appropriate name).
File the new child PNR: enter F.
Modify the original PNR if needed — rebook or cancel segments as required.
Add received from again: enter 6VICKIE (replace VICKIE with the appropriate name).
End the transaction: use E, ET, or er.

Critical

Sabre divides by name field, not by passenger number. A name field like 2SMITH/JOHNMR/KATHYMRS contains two passengers. D1 divides the entire field; D1.1 divides only the first passenger in that field. Always confirm the name field structure with *N before dividing.

For the full Sabre entry library, see the Sabre commands complete reference. For queue filing after splitting, read Sabre queue: a quick guide for managing PNRs.

Master Comparison: Split PNR Commands Across All Three GDSs

Task	Amadeus	Galileo	Sabre
Divide one passenger	`SP3`	`DP1`	`D1`
Divide multiple passengers	Repeat `SP` entries	`DP1-3.6`	`D146`
Divide group passengers	Via `SP` by line	`DG/10`	Via `D` by name field
Divide named + unnamed	Not applicable	`DG/5.P21-23`	Not applicable
Display divided records	Automatic display	`*DV`	Automatic display
Add received from	`RF P`	`R.M`	`6P`
File new PNR	`EF`	`F`	`F`
End transaction	`ET` / `ER`	`ER`	`E` / `ET` / `ER`

Important

Command availability and exact syntax can vary by GDS version, host configuration, agency profile and market. Always confirm in your training environment before using a split command on a live booking.

What Happens to the Booking After a Split

Understanding the mechanics prevents surprises. After a split, both records undergo specific changes.

Element	Original PNR	New Split PNR
Passengers	Remaining passengers only	Divided passengers only
Flight segments	Retained for remaining passengers	Copied for divided passengers
Record locator	Unchanged	New record locator assigned
Fare and pricing	Must be re-priced if passenger count changed	Must be newly priced
Ticketing arrangement	Often needs re-entry	Must be re-entered
Seat assignments	May be lost for divided passengers	Must be re-selected
SSRs and OSIs	Retained for remaining passengers	Usually copied — always verify
Queue placement	Must be re-filed	Must be filed manually

Always re-price after splitting

When the passenger count changes, the original fare quote becomes invalid. Re-price both records using the Amadeus FXD guide or the Galileo FS guide.

Common Mistakes When Splitting PNRs

Forgetting the received-from field. Every record needs a valid received-from entry before it can be filed. Missing it leaves the PNR incomplete.
Assuming fares carry over. Splitting changes the passenger count, which invalidates the original fare. Always re-price.
Dividing the wrong passenger in Sabre. Sabre divides by name field, not passenger number. Confirm the name field structure first.
Not checking SSRs after splitting. Special service requests may or may not follow the divided passenger — always verify.
Leaving queue placement undone. The new PNR sits in your work area until you file it. Use the queue commands for your host.
Splitting a ticketed PNR without checking reissue rules. If the original was already ticketed, the new record needs its own ticket — and the original may need voiding or reissuing. See reissue vs revalidation.
Forgetting to update contact details. The divided passenger may need a different email or phone number. See how to add contact details.

Best Practices for Splitting PNRs

Display the PNR before splitting. Confirm passenger line numbers and name field structure so you divide the correct traveller.
Complete both records. After filing the split, return to the original and add the received-from field and end transaction.
Verify the new record immediately. Check that the correct passengers, segments and SSRs moved across.
Re-price both records. Never assume the original fare still applies.
Re-select seats if required. Seat assignments are frequently lost in a split.
File to the correct queue. Both records may need different queue routing — use the Amadeus, Galileo or Sabre queue guides.
Document the split. Add a remark or vendor remark explaining why the booking was divided.

For group bookings, splitting is often the first step before individual servicing. See the cross-GDS group booking guide for the full workflow.

Frequently Asked Questions

What is the difference between splitting and cloning a PNR?

Splitting divides passengers from one PNR into separate records — the original PNR remains but with fewer passengers. Cloning duplicates the entire PNR into a new record without modifying the original. For cloning, see how to clone a PNR.

How do I split a PNR in Galileo?

Use DP followed by the passenger number. For example, DP1 divides passenger 1, and DP1-3.6 divides passengers 1, 2, 3 and 6. For group bookings, use DG/10 to divide 10 unnamed passengers. Then file with F, sign with R.M, and end with ER.

How do I split a PNR in Amadeus?

Use SP followed by the passenger number — for example, SP3 splits passenger 3. Then add RF P (received from), file the split PNR with ef, add RF P again on the original, and end with ET or ER.

How do I split a PNR in Sabre?

Use D followed by the name field number. For example, D1 divides name field 1, D1*4*6 divides fields 1, 4 and 6, and D1.1*1.2 divides the first two passengers in name field 1. Then add 6P, file with F, add 6VICKIE, and end with E, ET or ER.

Does the fare carry over when I split a PNR?

No. Splitting changes the passenger count, which invalidates the original fare quote. You must re-price both the original and the new PNR. Use the Amadeus FXD guide or the Galileo FS guide to reprice.

What happens to SSRs and special meal requests after a split?

SSRs and OSIs are usually copied to the new record, but this is not guaranteed across all hosts and carriers. Always verify the new PNR and re-add any missing service requests. For wheelchair requests, see the WCHC, WCHR and WCHS guide.

Where can I practise split PNR commands safely?

Use your GDS training mode or a dedicated training PCC. The GDS training hub includes structured lessons, and you can test your knowledge with the Galileo exam or the Amadeus basics exam.

Final Thoughts

Splitting a PNR is one of the most common servicing tasks in any GDS. Whether you are separating a family onto different return flights, dividing a corporate group, or preparing a partial ticketing run, the split commands are essential daily tools.

Keep the core entries in mind: DP in Galileo, SP in Amadeus, and D in Sabre. Always confirm the passenger or name field structure first, complete both records with the received-from field, and re-price the booking after the split.

The golden rule: a split creates two bookings where there was one — both must be complete, correct and priced before you move on.

Keep Building Your GDS Skills

Explore more command references, step-by-step tutorials and practice exams on GDS Hub.

Split PNR Guide Clone PNR Guide Transfer PNR Group Booking Guide Amadeus Commands GDS Training Hub

🏷 Tags: amadeus PNR Split