/
10. ERROR HANDLING

10. ERROR HANDLING

Each response from GP Travel HUB contains identifier whether it has been processed successfully or not - the elements <Success/>, <Warning/>, <Errors/>.

There are the following possible cases:

10.1. SUCCESS

Means that request was successfully sent and GP Travel HUB receives correct response from supplier without any warnings and errors from supplier.

<OTA_CancelRS Version="2" EchoToken="EchoToken" TransactionIdentifier="12232" xmlns:ota="http://www.opentravel.org/OTA/2003/05"> <Success/> </OTA_CancelRS>

10.2. WARNING

Means that request was successfully sent and GP Travel HUB receives correct response from supplier, but there are some warnings to pay attention.

There is a structure of Warning Response that is common for every response.

Warnings/Warning:

*mandatory

Element

Attribute

Type

Description

Min…Max occurs

Element

Attribute

Type

Description

Min…Max occurs

 

Type*

integer (1, 3, 10, 11)

Defines type of the error or warning that occurred. Refers to OTA codes "Error Warning Type (EWT)”.

1…1

Code*

integer (1 - 1051)

Defines Error/Warning code.

1…1

Status*

string ("SENT", "NOT_SENT")

The values are (SENT | NOT_SENT). Used for defining actual status of request.

1…1

ShortText*

string

Short error description.

1…1

RecordID

string

This attribute specifies supplier ID. If requests spans multiple suppliers, you can use this attribute to identify which supplier caused the problem.

0…1

Language*

 

For more information see Common Data Description section in Glossary.

 

DocURL

URI

If present, this URL refers to an online description of the error that occurred.

0…1

Tag

string

If present, this attribute may identify an unknown or misspelled tag that caused an error in processing.

0…1

<Warnings> <Warning Code="189" Language="en" RecordID="supplierCode" ShortText="Price has been changed." Status="SENT" Type="3"/> </Warnings>

10.3. ERROR

Means that request was not sent to supplier (supplier temporally unavailable or failed data verification) or GP Travel HUB receives incorrect response or error from supplier. In case of error GP Travel HUB additionally returns original text from supplier.

Either there can be errors returned by GP Travel HUB itself. It mostly can be cases when a request validation not passed. Requests with incorrect format can not be processed by GP Travel HUB and passed to suppliers, so GP Travel HUB returns SOAP error message.

<Errors> <Error Type="3" Code="172" ShortText="Generic error." Status="NOT_SENT" Tag="NORMAL" Language="en">Invalid client specified [ID:stb, IDContext: null, Instance:null]</Error> </Errors>

10.4. ERROR AND WARNING CODES

Here we list all possible errors and warnings that can occur at excursion messages.

10.4.1. EXCURSION SEARCH

Warning/
Error

Code

Short text

Possible reason

Status

Error

172

Requested action not possible.

  1. No information found for the requested city.

  2. The supplier supports search only by city code at this step.

NOT_SENT

Warning

172

Requested action not possible.

Requested language is not supported by supplier.

NOT_SENT

10.4.2. EXCURSION SCHEDULE

 

Warning/Error

Code

Short text

Possible reason

Status

Error

172

Requested action not possible.

  1. The supplier supports search only by excursion code at this step

  2. No information found for the requested date period

  3. No information found for the requested excursion code

NOT_SENT

10.4.3. EXCURSION AVAILABILITY

10.4.4. EXCURSION CHARGES

10.4.5. RESERVATION INITIATE

10.4.6. RESERVATION CONFIRMATION

10.4.7. RESERVATION IGNORE

10.4.8. EXCURSION RETRIEVAL

10.4.9. CANCELLATION INITIATE

10.4.10. CANCELLATION CONFIRMATION

10.4.11. CANCELLATION IGNORE

10.4.12. EXCURSION DESCRIPTIVE INFO

 

Related content