Term Definition GMT Greenwich Mean Time MPTB

Term
GMT
MPTB
DOB
SnD
CUC
#
Definition
Greenwich Mean Time
Master Pricer Travel Board
Date of Birth
Slice And Dice
Currency Conversion
Check
1.
Common Checks
Application should not accept the special characters.
Post a successful booking creation, clicking Back Button on the
browser/application shouldn‟t create duplicate PNR.
Where application session (i.e. State-less and State-full) is inactive from nearly
14 minutes, session should be signed out.
A minimum of one alphabet is accepted in the PAX - first name fields.
A minimum of 2 alphabets are accepted in the PAX - second name fields.
With the given infant‟s DOB, infant‟s age must fall within the age range: >=1 day
and <2 years.
With the given Child‟s DOB, Child‟s age must fall within the age range: <=2 days
and <12 years.
Applicable process workflows are correctly followed.
HR (Hann Air) recommendations should not display in the domestic trip. Note:
Same should be blocked.
International point(s) should not display in the domestic trip. Note: Same should
be blocked.
LCC/Ticketless carriers should not display in the search results as Amadeus
Web services do not support the same.
Where Segment Sell is done in the standard access, application should ignore
and sign-out immediately after the PNR_AddMultiElements (option Code 0)
response.
2
MPTB Search
Proper pricing types:
i) RP, RU, TAC, ET, PTC should be passed in the request (domestic).
ii) RP, RU, TAC, ET should be passed in the request (international).
Total count of the suggested recommendations should be passed correctly in
the request.
A maximum of 9 seats (including for both Adult and Child PAX types) should be
booked in a booking. Note: Infants are not allocated any seats.
Breakpoints should be correctly applied...
MPTB request and response should have the same version.
MPTB search is only allowed till next 361 days from the current date.
MPTB search is not allowed for dates prior to the current date.
Return date is not before the Start date.
Selected class is passed correctly in the request.
Validating carrier information is correct in the below tag:
<transportStageQualifier></transportStageQualifier>
Note: In case of multiple validating carrier pick first carrier that comes after the
tag <transportStageQualifier>
SnD in international (if applicable).
CUC in both domestic and international (if applicable).
Yes/
No
3
Sell
Proper Sectors (origin and destination) are passed in the query.
Proper classes are passed in the query.
Correct no. of seats are requested. No seat for infant.
Sell request must not be used to check availability.
Sign-out is applied immediately where the sell has failed.
Sell is successful where status of all the segments is „OK‟ in the Sell response.
Sell is failed where status of any of the segments is UNS, RQ, X.
4
AddMultiElements
All the mandatory elements (AP, FP, TK, NM) are added (in option Code 0)
Passport details are correctly passed for International bookings (option Code 0).
Element FM is applied (option Code 0).
Note: FM is either mandatory or optional depends on Customer on how they
apply Commission.
Process should be stopped and signed-out where any status other than HK is in
response (option Code 0).
OT numbers should be incremental (option Code 0)
Response shouldn‟t have any error with the error code ERR (option Code 0)
PAX names and segment details are applied (option Code 0)
No NHP remark in the response (option Code 0).
RF element information is passed in the request (option code 10).
GDS PNR is retrieved in the response (option code 10).
5
Pricing
Correct price type applied in the request: (RP, RU, PTC and FBA for domestic)
and (RP, RU and RLO for international).
Correct Fare Basis applied in the request (tally from MPTB response) – Only for
domestic booking.
Correct breakpoints applied in the request (tally from MPTB response) – Only
for domestic booking.
Correct segment numbers applied in the request (tally from
PNR_ADDMULTIELEMENTS response).
The user is notified where the fares have changed from what was displayed in
the MPTB result. Booking process is continued only where the user has
approved on the fare change.
Validating carrier is correctly passed in the request
TST numbers are correct as per passenger type information given. TST are
created as per PTC.
<fareBasisCode></fareBasisCode> tag is not applied in the request where the
Fare Basis Code is of either 3 or less than 3 digits.
6
TST Creation
TST request executed with the correct TS numbers.
Proper TST numbers and sequence numbers are received in the response.
7
PNR Saving (PNR_Retrieve)
Mandatory element RF is added in the PNR
Where Airline record locator is not returned in PNR_Retrieve after saving then a
loop of PNR_ADDMultiElements (option code 21) must be applied at an interval
of 3-5 seconds after the PNR_Retrieve.
Check the Airline PNR in the response along with all the details transmitted so
far.
Post ticketing 13 digit ticket number should be there in the response for each
PAX in FB and FA element.
8
Ticketing (Doc_Issuance)
FP, FV and TK are added properly.
Passport details are added for the international bookings.
Response should have “OK Ticket”
“Simultaneous changes Error” is handled as per the suggested practice.
09
Session Pooling
MPTB request should be applied using the session from the pool.
Dedicated Session should be closed
Sequencing in each session should be incremental and in order. (Can be
verified via logs and from tracer tools)
Auto- Closure of any session which has been inactive from past 14 minutes.
Should be closed within 14 minutes
Booking (PNR Creation) will be done in dedicated session
MPTB Search, and Informative Pricing (fare Rules) is done via session pooling.
PNR Split, Full PNR Cancellation and Element Cancellation
PNR should be successfully retrieved before PNR Split, Full PNR Cancel or Element Cancel is
applied.
Note: This is a common check.
PNR_Split, PNR Cancel or Element Cancellation should not be applied where MOD status is
received in the PNR_Retrieve response.
Note: This is a common check.
With PNR_Split a child PAX may or may not be left alone in the booking. This will depend on the
TMC‟s business rule.
Note: This is a common check.
Cancellation Request of Infant should be applied with that of linked Adult and vice versa.
Note: This is a common check.
Air segment of the flight that has flown shouldn‟t be cancelled.
Note: This is a common check.
Mandatory elements shouldn‟t be cancelled individually in the PNR and at least one of each
should be left in the active PNR.
Note: This is a common check.
Option code 0 (for No special processing) should be used in PNRActions tag in the
PNR_Cancel Request.
PNR_Cancel request -> Tag Cancelelements -> Tag Entry Type should have value:
 „I‟ where complete itinerary cancellation is required.
 „E‟ where a particular or multiple element cancellation is required at the same time.
Should entry type „E‟, element Identifier (OT/ST) and its line number must be requested.
PNR_Cancel Response should have below details:
1. Tag "isPNRModifDuringTrans" with value "MOD".
2. Element details which are requested to cancel either full PNR or a particular element type.
Mandatory element RF is added in the PNR
Verify if Full PNR Cancellation or Element Cancellation is done successfully.
At least one PAX must be left in the original PNR and PNR Split can be applied on the
remaining PAX in the PNR.
For partial cancellation, PNR_Split request should have the element type “PT” for passenger
tattoo and Tattoo (number) of the passenger to split.
Where no PNR has been retrieved, the user should add the record locator in the request.
16.

Download Report