This task can be used to retrieve and display canned remarks from PNR.
Transaction Name:
TicketInfoDisplay_5
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.
General knowledge about a PNR/BF.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
None.
Request:
Unless otherwise specified, use ALL CAPS in any request data.
Retrieve by Record Locator can only be performed on the same core.
For sessionless environment, <PNRBFRetrieveMods> (2024) request is required first. See the sample page for a PNR/BF request by record locator sample. Also, see Task PNR Retrieve by Record Locator in the PNRBFManagement transaction documentation.
In sessioned environment, a PNR can be retrieved using <PNRRetrieveMods> within TicketInfoDisplay_5. The ticketing information may be retrieved at the same time within the same request. The bullets in the previous paragraph still apply.
The <PNRCannedRemarkMods> (4040) doesnt have any related tags. It returns all canned remarks attached to the PNR/BF in the <CannedRemarkInfo> (DPRM) tag.
Prerequisite tasks:
If this task is used with <PNRBFRetrieveMods> (2024) request, no prerequisite tasks are required.
If only the <PNRCannedRemarkMods> (4040) is in the request, the PNR/BF must be retrieved first. For example, the PNR can be retrieved by the record locator, as specified in the previous Request section.
Expected response:
PNR Retrieve
The response from a retrieve of the currently active PNR/BF is a <PNRBFRetrieve> (2025), with all of the PNR/BF data requested in the specified elements as listed in Section 3. If a <RequiredData> element is in the request, only the types of data requested in <RequiredData> element are returned in the <PNRBFRetrieve>.
<Control> is always the first element in a non-error response. This element contains the information about the remainder of the response, including the total number of main elements, and the Record ID and number of each type of main elements returned.
Following are any items with special characteristics.
Form of Payment
For Form of Payment, one of three elements are returned: <CreditCardFOP>, <CheckFOP>, and <OtherFOP>. Only one Form of Payment can be added to a PNR/BF, so only one of these three elements is present in the response.
Name
The <LNameInfo> and <FNameInfo> elements are for Last Name and First Name, respectively. The number of <LNameInfo> and <FNameInfo> elements is shown in the <Control> element, but may not reflect the order exactly.
If there is more than one surname in the PNR/BF, a set of <LNameInfo>/<FNameInfo> elements exist for each Last Name/First Name combination.
If there is only one surname but multiple first names, only one <LNameInfo> exists, followed by a <FNameInfo> for each first name.
Itinerary
For all types of Itinerary (Air, Car, Hotel, etc.), there are primary elements, which have the basic itinerary information, and secondary elements, which have additional information such as Change of Gauge, Operated By, and Optional Car or Hotel data.
The order for this information is Primary followed by any Secondary(s) that apply to the Primary. For example, an <AirSeg> element followed by an <AirSegOpAirV> followed by an <AirSegDetail> followed by the next <AirSeg> element.
The order of the Primary Itinerary elements is determined by their location in the PNR/BF. The maximum number of Itinerary items in a PNR/BF is 99, so the combination of all types of Primary Itinerary elements cannot exceed 99. The total number of each Primary and Secondary elements is shown in <Control>, but may not reflect the order exactly.
Seats
For seat information, there is a <SeatSeg> element for each segment. Following the <SeatSeg> is be a <SeatAssignment> element for each passenger for that segment. The total number of <SeatSeg> and <SeatAssignment> elements is shown in the <Control> element, but may not reflect the order exactly.
Special Services (SSRs) and Other Special Services (OSIs)
For Special Service Information (SSRs), there is a <NonProgramaticSSR> (Manual SSR) element or <ProgramaticSSR> element for each SSR. There is an <OSI> element for each OSI. The combination of SSRs and OSIs cannot exceed 255 in the PNR/BF.
The <NonProgramaticSSR>/<ProgramaticSSR> elements are in the order they are in the PNR/BF and, therefore, may be mixed. In addition, if there is free text for a Programmatic SSR, the <ProgramaticSSRText> element, which immediately follows the applicable <ProgramaticSSR> element. The total number of <NonProgramaticSSR>, <ProgramaticSSR>, and <ProgramaticSSRText> elements is shown in the <Control> element, but may not reflect the order exactly.
Ticketing Arrangement
For ticketing arrangement, there is a possible one of five elements that can be returned: <TkArrangement>, <TAUTkArrangement>, <TAWTkArrangement>, <TLTkArrangement>, and <TAMkArrangement>. Only one type of Ticketing Arrangement can be added to a PNR/BF, so only one of the five elements is present in a response.
PNR Canned Remark
Any canned remarks available displays in the <PNRCannedRemark> (4041).
Error and warning responses:
The most common error response for the <PNRRetrieve> is an error that the Record Locator or File Address is not valid for a PNR/BF.
For the <PNRCannedRemark>, the following errors can display:
Follow-on requests:
If request was used in sessioned environment there are numerous follow on requests possible. You can display a fare, update PNR/BF, etc. It is highly recommended to End-transact or Ignore the PNR/BF. For example, with the PNRBFManagement transaction, follow the steps in Task Finish Active PNR/BF or Task Ignore Active PNR/BF.
Retrieve by Record Locator (same core)
<PNRBFRetrieveMods>
Terminal Equivalents:
Apollo: *123ABC
Galileo: *123ABC
Ordering
KLR
Min/Max
XML Tag
BP02
1 1
<PNRAddr>
BP06
0 1
<RequiredData>
Retrieve Canned Remarks
<PNRCannedRemarkMods>
Terminal Equivalents:
Apollo:
Galileo:
Ordering
KLR
Min/Max
XML Tag
Response by Record Locator (same core)
<PNRBFRetrieve>
If PNR/BF 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
<TAMkArrangement>
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
<HtlSegOptFlds>
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>
O
DPR1
0 99
<ItinRmk>
P
ST01
0 99
<SeatSeg>
P
ST02
0 9801
<SeatAssignment>
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>
EE
BP40
0 99
<Email>
FF
BP41
0 1
<CorporateID>
GG
BP42
0 1
<DividedBookingInfo>
HH
BP45
0 99
<AdditionalID>
<PNRBFRetrieve>
If error occurred
Ordering
KLR
Min/Max
XML Tag
EROR
1 1
<ErrText>
Response by Canned Remark
<PNRCannedRemark>
Ordering
KLR
Min/Max
XML Tag
DPRM
0-99
<CannedRemarkInfo>
<PNRCannedRemark>
If Error Occured
Ordering
KLR
Min/Max
KLR Name
EROR
1-1
<ErrText>