Home โ€บ Blog โ€บ Amadeus NP Command: Create & Cancel NONAME Elements Guide

Amadeus NP Command: Create & Cancel NONAME Elements Guide

Amadeus NP command NONAME element guide for group PNRs

Amadeus NP Command โ€” Create and Cancel NONAME Elements

A complete guide to the Amadeus NP command โ€” how to create or cancel NONAME elements for passengers in a group PNR when individual names are not yet available.

โšก Key Takeaways

  • NP15 creates a NONAME element for 15 unnamed passengers โ€” holding group space before names are known.
  • NP2,3,5 creates multiple NONAME elements in one entry โ€” useful for sub-groups with different requirements.
  • NP0 cancels existing NONAME elements once names have been finalised.
  • NONAME elements hold space but do not replace the airline’s name submission deadline.
  • Always transmit names before the deadline with NT or NTSR, or the airline may auto-cancel the group.

Group bookings rarely start with a complete list of passenger names. Travel agencies often hold group space weeks or months before the travellers are finalised, and the airline allows the group to be reserved without submitting individual names straight away. The Amadeus NP command exists for exactly this situation. It creates a NONAME element that reserves a specific number of places for passengers whose names are not yet available, letting the booking be held and priced while the agency collects the traveller details.

What Does the Amadeus NP Command Do?

NP is the Amadeus GDS command used to create or cancel NONAME elements for passengers in a group PNR.

Category: Group Booking.

The Amadeus NP command allows you to specify the number of passengers whose names are not yet available in a group booking.

A NONAME element holds the required number of unnamed places in the group. The booking is secured, priced, and managed as normal, but the individual passenger names are added and transmitted later using the standard name entries and the NT / NTSR commands.

Amadeus NP Command โ€” Create a NONAME Element

The simplest form of the Amadeus NP command creates a single NONAME element for a specific number of passengers. This is the most common variation โ€” you know the group size but not yet the individual names.

Create a NONAME element for 15 unnamed passengers:

NP15

This creates a NONAME element for 15 passengers. The group space is held for 15 unnamed travellers until the individual names are submitted.

Amadeus NP Command โ€” Create Multiple NONAME Elements

When the group is made up of sub-groups with different requirements โ€” separate rooming groups, different passenger types, or travellers arriving on different dates โ€” you can create several NONAME elements in one entry.

Create multiple NONAME elements in a single entry:

NP2,3,5

This creates multiple NONAME elements for 2, 3, and 5 passengers separately. Use it when different sub-groups need their own unnamed element in the group booking.

Amadeus NP Command โ€” Cancel NONAME Elements

Once the individual names have been finalised and added to the PNR, the NONAME placeholders are no longer needed. The Amadeus NP command also cancels them.

Create or cancel NONAME elements easily using the Amadeus NP command:

NP0

This cancels the existing NONAME elements in the PNR. Use it when the names have been finalised and the unnamed placeholders are no longer needed, or when the group composition has changed and the NONAME elements must be re-created.

When to Use the Amadeus NP Command

Use the Amadeus NP command when creating or managing a group PNR where passenger names are not yet available, allowing the required number of unnamed passengers to be held in the booking. Typical scenarios include:

  • Holding group space before the final passenger list is confirmed.
  • Reserving places for a group whose individual travellers are still being collected.
  • Managing sub-groups within a larger booking that have different requirements.
  • Holding a block of seats for a tour or incentive group still in the sales phase.
  • Adjusting the number of unnamed passengers when the group size changes.
  • Cancelling NONAME elements once the names have been finalised and submitted.

How It Fits Into Your Group Booking Workflow

A typical group booking session using the Amadeus NP command might look like this:

  1. Create the group name element with NG15EUROPE TOUR.
  2. Search group availability with AN07JULLONSYD/RGRP.
  3. Sell the group space using SS15G3/SG or waitlist with SS15C4/PG.
  4. Add the NONAME element with NP15 to hold the unnamed places.
  5. Collect the individual names and add them to the PNR.
  6. Cancel the NONAME element with NP0 once names are finalised.
  7. Transmit the names to the airline with NT or NTSR.
  8. Issue the group tickets with TTP.

Amadeus NP Command โ€” Quick Reference Table

Command What It Does
NP15Creates a NONAME element for 15 unnamed passengers
NP2,3,5Creates multiple NONAME elements for 2, 3, and 5 passengers
NP0Cancels existing NONAME elements in the PNR

How the Amadeus NP Command Relates to Other Group Booking Commands

The Amadeus NP command works alongside the broader group booking toolkit in Amadeus. Here is how it relates:

  • NG โ†’ creates a group name element.
  • AN/RGRP โ†’ displays group availability.
  • SS/SG or SS/PG โ†’ sells confirmed or waitlisted group space.
  • NP โ†’ creates or cancels NONAME elements for unnamed passengers.
  • SRGRPF โ†’ adds a Group Fare SSR element with a remark.
  • RTN / RTNR โ†’ display individual passenger names in a group PNR.
  • NT / NTSR โ†’ transmit group passenger names to airlines.
  • TTP โ†’ issues the group tickets once names are accepted.

The key distinction: the Amadeus NP command holds the space without names. The NT / NTSR commands submit the names โ€” they are the final step before ticketing. Non-NAME elements and name transmission must both happen on time to keep the group confirmed.

Important โ€” NONAME Holds Space Only

NONAME elements hold space, but they do not replace the airline’s name submission deadline. The individual names must still be added and transmitted to the airline before the deadline, or the group space will be automatically cancelled.

Always track the airline’s deadline carefully and confirm the NONAME element matches the actual expected group size. If the number changes, update the NONAME element before finalising the names. For the full audit trail of group PNR changes, use RH.

Official Amadeus Documentation

For the authoritative reference on group booking commands and Amadeus group NONAME elements, refer to the Amadeus Altรฉa Suite documentation โ€” the official source for all Amadeus group booking commands including NG, NP, NT, NTSR, and RTN.

Frequently Asked Questions About the Amadeus NP Command

What does the Amadeus NP command do?

The Amadeus NP command creates or cancels NONAME elements in a group PNR โ€” holding space for passengers whose names are not yet available.

What does NP15 do in Amadeus?

NP15 creates a NONAME element for 15 passengers, holding the group space for unnamed travellers until individual names are added. It is the most common form of the Amadeus NP command.

What does NP0 do?

NP0 cancels the existing NONAME elements in the group PNR. Use it when names have been finalised or the group composition has changed. It is the cancellation counterpart of the Amadeus NP command.

Can I create multiple NONAME elements in one entry with the Amadeus NP command?

Yes. Use NP2,3,5 to create separate NONAME elements for 2, 3, and 5 passengers โ€” useful for sub-groups with different requirements.

Do NONAME elements replace the need to submit names?

No. NONAME elements only hold space. The individual names must still be added and transmitted to the airline before the name submission deadline, using NT or NTSR.

Conclusion

The Amadeus NP command allows group bookings to be held before the final passenger list is known. Use NP15 to create a NONAME element for a set number of passengers, NP2,3,5 to create multiple elements for sub-groups, and NP0 to cancel the elements once names are finalised.

Remember that NONAME elements hold space but do not replace the airline’s name submission deadline โ€” always track the deadline carefully and transmit names in time with NT or NTSR. The Amadeus NP command is the placeholder that buys you time, not the final step.

Paired with NG, AN/RGRP, SS/SG, RTN, and TTP, the Amadeus NP command ensures every group booking is held, managed, and finalised accurately โ€” from the first name element to the final ticket for every passenger.

Want to Practice the Amadeus NP Command?

Open our free GDS terminal simulator and run NP, NG, AN/RGRP, NT, NTSR, and every other group booking command in a safe, risk-free environment.