

        📚 GDS Academy

        
            
                
                    Amadeus GDS Commands & Lessons | GDS Hub
                    34
                

            
                
                    Galileo GDS Commands & Lessons | GDS Hub
                    26
                

            
                
                    Sabre GDS Commands & Lessons | GDS Hub
                    20
                

                    

        
            🛠 Tools
            Airport Taxes Database
            Airports Database
            Farebase Generator
            Tax Checker
            Airline Special Services

Amadeus Ticket Issuance Error: Fix EDIFACT Message Size Limits

A complete step-by-step guide for travel agents using Amadeus and GDS systems.

Travel agents and reservation system users often encounter a recurring amadeus ticket issuance error when trying to issue flight tickets. In many cases, the problem is caused by an incorrect passenger name format or by an EDIFACT message that exceeds the allowed size limit. This error halts the ticketing process, wastes valuable time, and creates frustration for both agents and customers. This guide explains the common causes, provides practical solutions, and shows the exact commands needed to issue tickets successfully while keeping your PNR open.

Common Causes of the Amadeus Ticket Issuance Error

This error usually occurs for one of the following reasons:

1. A space between the first name and the title in the passenger name field.

Example: PASSENGER/J MRS — there is a space between J and MRS. This format is often rejected because the name field must follow a specific structure.

2. Issuing tickets for all passengers at the same time.

When you issue all tickets together, the EDIFACT message may exceed the size limit, especially for large bookings or multi-airline itineraries.

3. Airline character limits for ticketing messages.

Some airlines impose a maximum message size. If the ticketing message exceeds that limit, the system returns an error and stops issuance.

Solution 1: Correct the Passenger Name Format

The first step is to check and correct the passenger name format. Remove any space between the first name and the title.

Change this:

PASSENGER/J MRS

To this:

PASSENGER/JMRS

or:

PASSENGER/FIRSTNAME TITLE

The correct format depends on the airline’s requirement. For more details, refer to: HE NAME CHANGE. Correcting the name format not only prevents the error but also reduces mismatches with passports and tickets.

Solution 2: Issue Tickets One Passenger at a Time

Instead of issuing all passengers together, issue tickets individually. Enter the first command:

TTP/P1/RT

Then for the second passenger:

TTP/P2/RT

Continue this process for each passenger. The RT command keeps the PNR open, allowing you to issue the remaining tickets without interruption. This method reduces the EDIFACT message size and avoids the error entirely.

Step-by-Step Ticketing Checklist

Open the PNR and review all passenger details.
Remove extra spaces between the first name and the title.
Confirm the name matches the passport exactly.
Issue each ticket using TTP/P1/RT.
Check each system response to confirm successful issuance.
If the error continues, review airline limits or contact support.

Prevention Checklist

Keep each PNR to one passenger when the itinerary has many segments or unusually long names.
Format the name as SURNAME/FIRSTNAME MR and remove extra spaces before running TTP.
Check that every SSR, OSI and APIS item is linked to the correct passenger.
Confirm the form of payment and ticket stock are valid before issuing.
If the error repeats, split the PNR and issue each passenger separately.

Large group bookings are the usual trigger. Split the group into individual PNRs, keep the same fare basis and tour code, and issue each ticket with TTP/P1/RT. Recheck the TST after every split so the fare and taxes stay aligned. A clean PNR, a valid TST and one passenger per transaction are faster to ticket than a large group record that has to be split after the error.

Related Error Guides

Frequently Asked Questions

What causes the ticket issuance error?

It is usually caused by a space between the first name and title, or by an EDIFACT message that exceeds the allowed size limit.

How do I fix it quickly?

Correct the passenger name format, then issue tickets one by one using TTP/P1/RT.

What does TTP/P1/RT mean?

It issues a ticket for the first passenger while keeping the PNR open for the remaining passengers.

Conclusion

By following these steps, you can avoid the amadeus ticket issuance error caused by passenger name spacing or EDIFACT size limits. Always verify the passenger name format, and issue tickets one passenger at a time. For more information on commands, you can check amadeus commands. These practices speed up ticketing, reduce errors, and improve the overall customer experience for every travel agency.

🏷 Tags: amadeus Amadeus errors