Task: Divide Booking

This task document provides basic instructions for using the PNRBFDivide_8 transaction.

• For more complete documentation describing the use of PNRBFDivide_8 for a standard (non-stored fare) in conjunction with PNRBFManagement see Task: Divide Booking Standard Fare - Extended.
• For more complete documentation describing the use of PNRBFDivide_8 for a stored fare, in conjunction with PNRBFManagement and DocProdFareRequote, see Task: Divide Booking Stored Fare - Extended.

This transactions lets you divide or split a single booking into two different bookings. Previously, this functionality was available only through terminal emulation transactions. The Dividing bookings functionality is a method for users to manage their bookings with fewer keystrokes than using terminal emulation, and allows you to handle unique booking situations.

Section 1: Short Answer

Transaction Name:

PNRBFDivide_8

Can this task be performed in a sessionless environment?

No. Dividing a PNR/BF is a multi-step process that requires data from all entries to remain available throughout entire process.

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.

The user must understand the multi-step Divide process and the implications of dividing a PNR/BF.

Some data items are split between the original PNR/BF and the newly created PNR/BF.  Not all PNR/BF data remains in the original booking, and not all booking fields are moved to the newly created booking.

Special limits or distinct restrictions to the input data that may not be readily apparent.

There are two types of input:

• Input that requires splitting group name data.
• Input that requires dividing passenger name data. 

Dividing group name data can be combined with dividing the passenger name because there are elements for each type of data. PNR/BFs that do not contain group name data cannot use group name elements.

Section 2: Detailed Description

This section covers the specific step of identifying individually-named passengers or some number of unnamed passengers to be removed from the current multi-passenger booking, and put into a new "child" booking. The child booking will be created automatically when this request is processed, and will be given its own record locator.

To see information regarding the subsequent steps necessary to finalize and save both the modified parent booking and the newly created child booking (which are not done with this transaction) see the extended documentation.

Request

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

After retrieving a PNR/BF, divide the PNR/BF using the <BookingDivideMods> tag. Submit a Divide request using <BookingDivideMods> with the <Divide> child element.

The Divide action divides or splits specific passengers from the original PNR/BF into a new PNR/BF. This new PNR/BF contains passenger-specific items, as well as shared data items that relate to all passengers, such as inventory and SSRs.

Three types of Divide actions can be made this request:

• Dividing unnamed passengers/seats from a group PNR/BF.
• Dividing named passengers from a group or non-group PNR/BF.
• Combining the previous two Divide actions for a group PNR/BF that has both named and unnamed passengers.

Expected Response

See the tables in Section 3 for possible output responses. A <PNRBFRetrieve> (2025) response returns the new PNR/BF via the PNRBFManagement transaction, with the names and the PNR/BF data that was split out from the original PNR/BF. You must use PNRBFManagement to redisplay the new child PNR/BF.

Notes:

• See the <Divide> description in the Transaction Request for details.
• The new PNR/BF is held in a temporary status until the final End Transact (ET).
• After the new "child" PNR/BF and the current "parent" PNR/BF are filed and end transacted, the child booking has its own record locator and may be retrieved and modified independently of the parent booking.
• Any time a PNR/BF displays that has been part of a divide process, it contains information identifying it as a parent or child, and contains the record locators to any of its parents or children.

Prerequisite tasks:

A current, unchanged PNR/BF must be retrieved before submitting the Divide request using <BookingDivide>.

Error and warning responses:

The expected error response will be found in <ErrText> in the <BookingDivide> element.

Follow-on requests:

There are two possible follow-on inputs coupled with their responses.  The first is an <EndTransactionMods> with “file” as the ET action.  This would be followed by a <PNRBFRetrieve> booking display response of the original PNR/BF.  This display response should then be followed by a normal <EndTransactionMods> input with its corresponding response.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Related Samples

PNRBFDivide_8_s1

PNRBFDivide_8_s2

PNRBFDivide_8_s3