Task: Segment Cancel

This task cancels one or more segments in the itinerary.

Section 1: Short Answer

Transaction Name: 

PNRBFManagement_33

Can any other transaction(s) perform this same task?

Can this task be performed in a sessionless environment?

Yes.

Are the request and response identical on both the Apollo and Galileo systems?

Yes.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

Not applicable.

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

Not applicable.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

Number cancelled (array count), cancel request number, <SegNum> element.

An itinerary segment only exists if the client performs a reference sell or direct sell or an air or open segment or an ARNK segment using PNRBFManagement_33 Task: ARNK Sell.

Prerequisite tasks:

One or more segments need to exist in the itinerary before a cancel can be done.

Expected response:

Number of cancelled blocks returned (array count), number of hotel cancel confirmation numbers returned (array count), request number, <SegNum>, <Status>. A successful cancel returns a status of ‘XX’.

Error and warning responses: Number of cancelled blocks returned (array count), number of hotel cancel confirmation numbers returned (array count), request number, <SegNum>, <Status>.

1.  Scenario:  No itinerary exists.

2.  Scenario:  Cancel denied by vendor (marriage logic only).

3.  Scenario:  Non-numeric segment number.

4.  Scenario:  Processing error.

5.  Scenario:  System error.

Follow-on requests:

There are no follow-on requests.

Section 3: Tables

Request (Input) Tags

<SegCancelMods>

Terminal Equivalents:

Apollo:  Xn

Galileo:  Xn

Ordering

NWB

Min/Max

XML Tag

A

1040

1-1

<SegCancelMods>

Response (Output) Tags

<SegCancel>

 

Ordering

NWB

Min/Max

XML Tag

A

1041

1-1

<SegCancel>

 

Related Samples

PNRBFManagement_33_s14