/
6. ERROR HANDLING

6. 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:

6.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>

6.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>

6.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 element has the same structure as Warnings/Warning.

<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>

6.4. ERROR AND WARNING CODES

6.4.1. CM HOTEL AVAILABILITY

Warning/Error

Code

Short text

Possible reason

Status

Error

783

Room or rate not found

There is no active contract for this hotel.

SENT

Warning

436

Rate does not exist

Rate does not exist.

SENT

6.4.2. CM HOTEL AVAILABILITY NOTIFY

Warning/Error

Code

Short text

Possible reason

Status

Error

783

Room or rate not found

There is no active contract for this hotel.

SENT

Error

448

System error

Suppliers message.

SENT

6.4.3. CM HOTEL RATE AMOUNT NOTIFY

Warning/Error

Code

Short text

Possible reason

Status

Error

842

Rate not loaded

  1. Suppliers message.

  2. No active hotel contract found.

  3. There is no stored date period for requested tariff.

SENT

Error

448

System error

Suppliers message.

SENT

6.4.4. CM HOTEL RESERVATION NOTIFY

Warning/Error

Code

Short text

Possible reason

Status

Warning

172

Requested action not possible

Double request to the endpoint.

NOT_SENT

Error

448

System error

  1. Reservation has undefined status 'someStatus'.

  2. Unknown message.

  3. Can not parse reservation status.

  4. Request is received from unknown channelmanager.

NOT_SENT

Error

361

Invalid hotel

Suppliers message.

SENT

Related content