19. FLIGHT SPLIT
- Yana Brilevskaya
Analytics
Diagram 19.1. Flight Split HUB Flow.
HUB has an opportunity to split PNR number for several passengers and as a result made several bookings exist. This message involves the following stages:
Split Initiate (OTA_AirBookModify, TransactionStatusCode="Initiate", ModificationType="6");
Split Ignore (OTA_AirBookModify, TransactionStatusCode="Ignore", ModificationType="6");
Split Commit (OTA_AirBookModify, TransactionStatusCode="Modify", ModificationType="6");
To split a PNR code into separate pieces (depending on amount and types of passengers) user must set up a list of passenger's ID-s which will remain in current PNR. Then, after successful commit user will receive a following element:
<BookingReferenceID Instance="child" ID="DBZDMI"/>Note: GP HUB sets up passenger IDs only, not names, surnames for those passengers, who will remain in existing PNR. Other passengers will be splited to different PNR code.
WARNINGS AND ERRORS
All Warnings and Errors that could appear during Flight Split messages you can see in ERROR HANDLING section.