Task: Remove PNR/BF record from Queue

This task allows the user to remove a specify PNR/Booking File (BF) record from a Queue.

Section 1: Short Answer

Transaction Name:

QueueProcessing_3

Can any other transaction perform this same task?

This is the only transaction available to remove a PNR/BF record from a Queue.

Can this task be performed in a sessionless environment?

This task can only be performed in a Sessioned environment.

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

The request and response information is identical on both the Apollo and Galileo systems.

List any industry-specific knowledge required to understand this task.

None.

Explain any special limits or distinct restrictions.

None.

Section 2: Detailed Description

Request:

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

For a Remove PNR/BF record from Queue request, a <QueueMods> element is required with a <QueueRemoveSignOutMods> sub-element. The <QueueRemoveSignOutMods> must contain the action code for a Remove PNR/BF record from Queue (QR). The PNR/BF record that is active in the user’s Agent Assembly Area (AAA) is the record that is removed, so no data relating to the record is required.

Prerequisite tasks:

The user must first have signed into Queue and received a PNR/BF record. For additional information see the task document for Sign into Queue.

Expected response:

If there are additional PNR/BF records available on Queue, the response from a Remove PNR/BF record from Queue request is a <PNRBFRetrieve> that will contain PNR/BF data as listed in Section 3. For more information on the <PNRBFRetrieve> see the documentation for the PNRBFManagement transaction.

If there are no additional PNR/BF records on Queue, or if the user is not allowed access to any of the remaining PNR/BF records on Queue, a <QueueErrText> element is returned with a <TextMsg> sub-element that indicates “OFF Q”. In addition, the user is no longer signed into Queue.

Error and warning responses:

All errors are returned in a <QueueErrText> element with a <TextMsg> sub-element. The error text that is returned explains the error.

Follow-on requests:

There are no follow-on requests for this task.

Section 3: Tables

Request (Input) Tags

 

<QueueMods>

Terminal Equivalents:

Apollo _QR____

Galileo _QR___

 

 

Ordering

KLR

Min/Max

XML Tag

 

A

QUR2

0 – 1

<QueueRemoveSignOutMods>

 

Response (Output) Tags

 

<QueueErrText>

If no more available PNR/BF records are found or other error occurred

 

 

Ordering

KLR

Min/Max

XML Tag

 

 

TEXT

1 – 1

<TextMsg>

 

<PNRBFRetrieve>

If another available PNR/BF is found

 

 

Ordering

KLR

Min/Max

XML Tag

 

A

CTRL

1 – 1

<Control>

 

B

BP07

0 – 1

<HeaderLine>

 

C

BP08

0 – 1

<GenPNRInfo>

 

D

BP09

0 – 1

<PostScript>

 

E

BP10

0 – 99

<LNameInfo>

 

F

BP12

0 – 99

<FNameInfo>

 

G

BP14

0 – 99

<FreqCustInfo>

 

H

BP16

0 – 99

<PhoneInfo>

 

I

BP32

0 – 1

<TkArrangement>

 

I

BP33

0 – 1

<TAUTkArrangement>

 

I

BP34

0 – 1

<TAWTkArrangement>

 

I

BP35

0 – 1

<TLTkArrangement>

 

I

BP36

0 – 1

<TAMTkArrangement>

 

J

DPP0

0 – 1

<CreditCardFOP>

 

J

DPP1

0 – 1

<CheckFOP>

 

J

DPP9

0 – 1

<OtherFOP>

 

K

BP17

0 – 1

<AddrInfo>

 

L

BP18

0 – 1

<DeliveryAddrInfo>

 

M

IT01

0 – 99

<AirSeg>

 

M

IT02

0 – 99

<AirSegOpAirV>

 

M

IT16

0 – 99

<AirSegDetail>

 

M

IT13

0 – 99

<ARNK>

 

M

IT03

0 – 99

<HtlSeg>

 

M

IT04

0 – 99

 

M

IT05

0 – 99

<CarSeg>

 

M

IT06

0 – 99

<CarSegOptFlds>

 

M

IT07

0 – 99

<NonAirSeg>

 

M

IT09

0 – 99

<DuePaidInfo>

 

M

IT10

0 – 99

<FlygTaxiSeg>

 

M

IT11

0 – 99

<TourSeg>

 

M

IT12

0 – 99

<CruiseSeg>

 

M

IT14

0 – 99

<TrainSeg>

 

N

DPR1

0 – 99

<ItinRmk> (Associated Itinerary Remarks)

 

O

DPR1

0 – 99

<ItinRmk> (Unassociated Itinerary Remarks)

 

P

ST01

0 – 99

<SeatSeg>

 

P

ST02

0 – 9801

<SeatAssignment>
*See special information in Section 2 (The maximum number is unrealistic. However, 9801 is that maximum with 99 segments and 99 passengers per segment.)

 

Q

BP19

0 – 255

<OSI>

 

R

BP20

0 – 255

<NonProgramaticSSR>

 

R

BP21

0 – 255

<ProgramaticSSR>

 

R

BP22

0 – 255

<ProgramaticSSRText>

 

S

BP23

0 – 1

<CustID>

 

T

BP24

0 – 1

<ProfileClientFileAssoc>

 

U

BP25

0 – 3

<CustomCheckRules>

 

V

BP26

0 – 255

<GenRmkInfo>

 

W

BP27

0 – 99

<VndRecLocs>

 

X

BP28

0 – 99

<VndRmk>

 

Y

DPIR

0 – 99

<InvoiceRmk>

 

Z

BP29

0 – 99

<QMinder>

 

AA

DPIR

0 – 99

<InvoiceRmk>

 

BB

BP30

0 – 1

<Untranslatable>

CC

BP37

0 – 99

<NameRelatedData>

 

FF

BP40

0 – 99

<Email>

 

GG

BP41

0 – 1

<CorporateID>

 

HH

BP42

0 – 1

<DividedBookingInfo>

 

II

BP45

0 – 99

<AdditionalID>

 

Related Samples

QueueProcessing_3_s5