Skip Navigation

Delete

Lodging segment cancellation should be performed using the UpdateReservationRQ API.

Deleting a lodging product is a two step process:

  1. Send an UpdateReservationRQ request with a D operation for the product to be cancelled.
  2. Send the UpdateReservationRQ request with commitTransaction=“True” or an ET command.

Note: Requests may differ depending on when the delete operation is performed. Refer to the flow diagrams earlier in this guide and the examples below for more information.

Deleting lodging products from a PNR using host commands (e.g. X1, XI) is not available. The following error message will be displayed:

CANNOT CANCEL SEGMENT SUMMARY-NOT AUTHORIZED

Important! Hotel segments booked using the host commands (HOD/0H) cannot be cancelled using UpdateReservationRQ.

Sell ignore

When the delete operation is performed during booking, but before the commit operation for a lodging product, then the request should look like:

<ns3:UpdateReservationRQ Version="1.19.0" xmlns:ns3="http://webservices.sabre.com/pnrbuilder/v1_19" xmlns:or="http://services.sabre.com/res/or/v1_14">
    <ns3:RequestType>Stateful</ns3:RequestType>
    <ns3:ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true"/>
    <ns3:ReservationUpdateList>
        <ns3:ReservationUpdateItem UpdateId="ID_3">
            <ns3:ProductUpdate op="D" id="21"/>
        </ns3:ReservationUpdateItem>
        <ns3:ReceivedFrom>
            <ns3:AgentName>Agent</ns3:AgentName>
        </ns3:ReceivedFrom>
    </ns3:ReservationUpdateList>
</ns3:UpdateReservationRQ>

The id marked in this request is the unique ID of the lodging product. This information is not available from the host level, so to retrieve the id, call GetReservationRQ (or any other service enabled to retrieve information about the particular Product ID).

Note: the id of the product is not a segment sequence number observed in the host display. Refer to the sample response for GetReservationRQ for a product ID associated to the lodging segment.

Modify ignore

When the session is ignored or it times out, all changes made since the last commit are reverted. If one of these changes was modify, a modify ignore message is sent to the supplier. Modify changes cannot be ignored selectively (i.e. per segment as it is done for sell), they can only be ignored together with all other changes in the current session.

Cancel initiate

When a delete operation is performed for a confirmed booking (after the ET command), the request should look like:

<ns3:UpdateReservationRQ Version="1.19.0" xmlns:ns3="http://webservices.sabre.com/pnrbuilder/v1_19" xmlns:or="http://services.sabre.com/res/or/v1_14">
    <ns3:RequestType>Stateful</ns3:RequestType>
    <ns3:ReturnOptions IncludeUpdateDetails="false" RetrievePNR="true"/>
    <ns3:ReservationUpdateList>
        <ns3:ReservationUpdateItem UpdateId="ID_3">
            <ns3:ProductUpdate op="D" id="21">
                <ns3:Product>
                    <or:ProductDetails>
                        <or:ProductName type="HHL">Lodging</or:ProductName>
                        <or:Lodging>
                            <or:ResGlobalInfo>
                                <or:BookingInfo>
                                    <or:CancellationReason>
                                        Found a better rate
                                    </or:CancellationReason>
                                </or:BookingInfo>
                            </or:ResGlobalInfo>
                        </or:Lodging>
                    </or:ProductDetails>
                </ns3:Product>
            </ns3:ProductUpdate>
        </ns3:ReservationUpdateItem>
        <ns3:ReceivedFrom>
            <ns3:AgentName>Agent</ns3:AgentName>
        </ns3:ReceivedFrom>
    </ns3:ReservationUpdateList>
</ns3:UpdateReservationRQ>

The request should contain:

  • The lodging product id of the segment to be cancelled (the same as the Sell Ignore operation)
  • A CancellationReason to be sent to the supplier. The cancellation reason is mandatory for Booking.com reservations.

Note: The Cancel operation should be either confirmed with ET or ignored.

Deleting UC segment from PNR

It is possible to delete Unconfirmed Status (UC) segment by an Agent with help of UpdateReservation service:

<ns3:UpdateReservationRQ Version="1.19.0" xmlns:ns3="http://webservices.sabre.com/pnrbuilder/v1_19"
xmlns:or="http://services.sabre.com/res/or/v1_14" >
    <ns3:RequestType>Stateful</ns3:RequestType>
    <ns3:ReturnOptions IncludeUpdateDetails="true" RetrievePNR="true">
        <!--Subject Area is optional – it is added here to reveive the whole Lodging data in response-->
        <ns3:SubjectAreas>
            <ns3:SubjectArea>LODGING_CONTENT</ns3:SubjectArea>
        </ns3:SubjectAreas>
    </ns3:ReturnOptions>
    <ns3:ReservationUpdateList>
        <!-- UpdateId="ID_3” this is random value since this is not pointing anywhere -->
        <ns3:ReservationUpdateItem UpdateId="ID_3">
            <!-- id="110" is the segment id taken from the GetReservation Response sent before this operation-->
            <ns3:ProductUpdate op="D" id="110">
                <ns3:Product>
</ns3:Product>
            </ns3:ProductUpdate>
        </ns3:ReservationUpdateItem>
        <ns3:ReceivedFrom>
            <ns3:AgentName></ns3:AgentName>
        </ns3:ReceivedFrom>
    </ns3:ReservationUpdateList>
    <ns3:UpdateToken></ns3:UpdateToken>
</ns3:UpdateReservationRQ>

Deleting OX segment from PNR

An agent can delete OX segment using UpdateReservation service. If the Type B returned (inbound) was successful the user can use this delete function rather than performing a Change Segment Status. As part of this Delete function, PNR will move the OX segment to history and no message will be generated to CSL or the supplier