> For the complete documentation index, see [llms.txt](https://cee-systems.gitbook.io/tcp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cee-systems.gitbook.io/tcp/exchange-examples/error-responses.md).
# Error responses
1. Error response: **VERIFY DATE SEQUENCE IN ITINERARY**
Check flown segments in PNR using \*H
\*\*\*\*\* HISTORY H95TJ8
\*\* NON-ACTIVE PRODUCTS \*\*
1 JY 787 B 14JUL OGLBGI TK1 1300 1455 O\* - use this segment
2 JY 714 B 14JUL BGISLU HX1 1345 1430 O\*
3 JY 742 B 14JUL BGISLU TK1 1605 1650 O\* - use this segment
Outbound travel was changed by the carrier. Segment 2 cannot be used because departure from BGI is earlier than arrival to BGI.
***
2. Error response: **INVALID MODIFIER / INVALID DATE / INVALID FARE BASIS CODE**
**Field for PTC** - Passenger Type Code must be added only in section PASSENGERS
If **FQ date** is not entered automatically by TCP, must be added by the agent.
**Account code** field, **only** account code can be here, **no any other information**
**Additional modifiers** field:
**Branded fare tier** must be shown with an asterisk and a colon (\*:) before BF. In this case \*:BF3.
If wrong or non-existing tier number is entered, Galileo returns the error response:
**Private fare** must be shown with a colon (:) before P (:P)
**Fare basis** field - **Fare basis with Ticket Designator** e.g THNI0QS6/NGTE.
**Ticket designator** (NGTE) is shown on ticket after Fare basis mostly separated by slash (/) and **can never be entered in Fare basis field**. Ticket designator will be added automatically.
CH or IN are also ticket designators and sometimes are not separated by slash – like KLXESKE1**CH**. Correct Fare basis is **KLXESKE1** and **PTC** is e.g. **C10 or CNN**.
Sometimes Fare basis shown on the ticket is not real Fare basis, but ticket code filed by the carrier. In such a case you have to check correct Fare basis on Fare display.
***
3. Error response: **SELECTED SEGMENT NUMBER TOO HIGH**
In case of partly used ticket, new fare calculation must be done from ticket origin. It means for the whole journey **including flown segments**.
***
4. **Upgrade to business class done by the carrier**
Original booking class for DXBDFW was Q and passenger was upgraded by the carrier to higher cabin (booking class P).
\*\*\*\*\* HISTORY GL0WTB \*\*\*\*\*
\*\* NON-ACTIVE PRODUCTS \*\*
1 EK 720 Q 21JUL NBODXB HK2 1635 2240 O\* 3
2 EK 221 P 22JUL DXBDFW HK2 215 940 O\* 3
In such a case Travelport - Galileo returns NO VALID FARE because booking class P is not correct for fare basis used (QLXEPKE1).
\>FQ/P1\*ADT/S1.2.4.6/CEK/.T17APR26
NO VALID FARE FOR INPUT CRITERIA
**Therefore, it is necessary to use pricing with fare basis. The warning -BOOKING CLASS FAILURE can be ignored in case of upgrade to higher cabin class done by the carrier.**
***
5. **Married segments - partly changed**
Selected segments: 1 / 2/ 3/ 5
Error response: **UNABLE TO FILE - SELECTION OUTSIDE OF MARRIAGE**
**It is necessary to ask for marriage removal first otherwise you cannot store the fare and exchange the ticket.**
