Task: Divide Booking - Stored Fare - Extended

This task document provides the complete overview of the Divide functionality with the PNRBFManagement transaction. The PNRBFDivide transaction allows you to 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_5

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?

No. See step 2. Dividing the PNR/BF using PNRBFDivide_5 in Section 2.

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 (Galileo CRS only).

Section 2: Detailed Description

Request

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

The entire Divide process contains multiple steps, which uses multiple transactions: PNRBFManagement (or related transactions), DocProdFareRequote, and PNRBFDivide_5.

1. Retrieving the PNR/BF.
2. Dividing the PNR/BF.
3. Verify the fare for the child PNR/BF.
4. Filing the PNR/BF.
5. Verify the fare for the parent PNR/BF.
6. End transacting for both records

The transaction can be ignored at any point up to the final end transact (ET).

1. Retrieving the PNR/BF Using PNRBFManagement

Request

Retrieve the PNR/BF using <PNRBFRetrieveMods>.

Response

The <PNRBFRetrieve> response returns a single PNR/BF. If the response is a similar names list, a PNR/BF must be selected from this list and subsequently displayed.

Notes

• There are several retrieval options using <PNRBFRetrieveMods>; all of these options are listed Section 3.
• After the PNR/BF is retrieved, it cannot be changed, except for dividing through the following steps.

2. Dividing the PNR/BF using PNRBFDivide_5

Request

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.

A user can divide named passengers on Apollo CRS using the DN code but cannot divide passengers from a group booking. On Galileo CRS, a user can divide passengers from a group or non-group booking using DG or DP codes respectively.

Response

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) in Step 6.

3. Verify the fare for the Child PNR/BF Using DocProdFareRequote

Request

Verify the fare by submitting <DocProdFareRequoteMods> (4028 Data Record).

• No elements are required in the <DocProdFareRequoteMods> tag.

Response

A <DocProdFareRequote>  response returns the <FareNumInfo> and a <DPOK> to verify the divided child fare.

4. Filing the PNR/BF Using PNRBFManagement

Request

File the newly created PNR/BF by including:

• A "File" action in the <EndTransactionMods> element.
  Note: This action type was added for PNRBFManagement.
• A value in the <RetrievedBy> element in the <EndTransactRequest>.

Response

A <PNRBFRetrieve> response returns the original PNR/BF, minus the divided names and name-specific elements, which now reside in the newly created PNR/BF.

Notes

• The File action stores the new, temporary PNR/BF until it can be successfully End Transacted in Step 4. Information pertaining to the new PNR/BF, including the record locator, is located in the <DivideBookingInfo> tag.
• The new PNR/BF cannot be retrieved by any means after it is filed and before it is End Transacted.

5. Verify the fare for the Parent PNR/BF Using DocProdFareRequote

Request

Verify the fare by submitting <DocProdFareRequoteMods> (4028 Data Record).

• No elements are required in the <DocProdFareRequoteMods> tag.

Response

A <DocProdFareRequote>  response returns the <FareNumInfo> and a <DPOK> to verify the divided Parent fare.

6. End Transacting Using PNRBFManagement

Request

An <EndTransactRequest> request to end transact modifications to both records. This request is a regular End Transact with an "E" action and a value in the <ReceivedBy> element.

An End Transact is required to complete the Divide process by finalizing:

• The newly created PNR/BF.
• The changes (removed passengers or seats) in the original PNR/BF.

Response

A successful response depends on the End Transact action input in the <EndTransactRequest> / <ReceivedBy> value.

Prerequisite tasks:

See the tables in Section 3 for possible input requests. A current, unchanged PNR/BF must be retrieved before submitting the Divide request using <BookingDivide>.

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.

Error and warning responses:

See the tables in Section 3 for possible error responses.  The expected error response will be found in <ErrText> in the <BookingDivide> element.

Follow-on requests:

After Step 6, there are no follow-on requests.

Section 3: Tables

Request (Input) Tags

Of important note: of the following four inputs to retrieve a BF or PNR, all must result in a single PNR or BF display.  A similar names list would require a subsequent display request resulting in a single PNR or BF display.

STEP 1: PNRBFManagement

Retrieve Booking by Passenger Name

Retrieve Booking by Record Locator

Retrieve Booking by Branch and Name

Retrieve Booking by Affiliate and Name

In the above, AFF would be the actual Affiliate Name.

Retrieve Booking by Flight Date and Name

Step 2: PNRBFDivide_5

Divide the retrieved booking

Step 3: DocProdFareRequote

Verify the fare for the divided Child booking

Step 4: PNRBFManagement

File the fare of the divided booking

Step 5: DocProdFareRequote

Verify the fare for the divided Parent booking

Step 6: PNRBFManagement

Create the new divide booking and finalize the original booking without the divided passengers present.
The response will redisplay the parent locator.

Response (Output) Tags

PNRBFManagement

PNRBFDivide_5

DocProdFareRequote

Related Samples

PNRBFDivide_5_s1

PNRBFDivide_5_s2

PNRBFDivide_5_s3

PNRBFDivide_5_s4

PNRBFDivide_5_s5

PNRBFDivide_5_s6

PNRBFDivide_5_s7

PNRBFDivide_5_s8

PNRBFDivide_5_s9