Reordering Segments

Reorder and Re-Store Fares: Apollo Only

Smartpoint does not currently offer automatic segment placement for Apollo (1V). By default, new or rebooked segments are placed at the end of the PNR.

Because Apollo's default order can result in segments that are no longer in chronological order, you can enable functionality to reorder segments and/or restore fares. You can enable Smartpoint to:

  • Automatically re-store fares as part of rebooking from a Low Fare Shopping response for either branded or unbranded fares.
  • Reorder segments and/or re-store fares using commands.
  • #RO Reorders the itinerary chronologically according to a precedence logic between segment types.
  • #RS Re-stores the stored fares.
  • #RORS Reorders the itinerary in the PNR and re-stores the stored fares (ATFQ).

Tip! Agencies that use the PNR Assist component can also reorder segments from Auto-Benchmarking. See PNR Assist Help for details.

Enabling and Disabling Reorder and Re-Store Fares

By default, Reorder and Re-Store Fares functionality is disabled. However, you can enable this functionality at any time.

Important! Your agency may already have a custom script or other method for enabling reorder and restore. Before you enable this feature, confirm with your Travelport Smartpoint administrator that there are no existing scripts that can cause a conflict.
To enable Smartpoint to reorder segments:

Enter #RORON.

To disable Smartpoint to reorder segments:

Enter #ROROFF.

Re-Storing Fares from Rebooking

If Reorder and Re-Store is enabled on Apollo, a message to reorder displays automatically when you rebook either branded or unbranded fares in a Fare Shopping (FS) flow.

You can either:

  • Click No to continue stop rebooking.
  • Click Yes to approve re-storing the invalidated fares and reordering segments, if applicable.

Smartpoint recreates (re-stores) the current stored fares in the PNR by:

  1. Determining the stored fares related to the segments that are going to be rebooked.
  2. Retrieving the original pricing entries used to store the fare (*T).
  3. Determining which stored fares need to be re-stored and which stored fares are not going to be replaced by rebooking.
  4. Reading the stored fare response to extract the price as booked ($B) from the ATFQ lines.
  5. Canceling the segments that are going to be rebooked and selling the new segments.
  6. Reordering the itinerary (following the same logic as the #RO function).

This command reorders the current itinerary based on:

  1. Departure time (standardized to UTC to handle multiple time zones in the itinerary).
  2. Precedence of segments based on type.

Segments are ordered based on the following rankings:

  1. Air segments
  2. Car rental segments
  3. Passive car segments
  4. Limousines and retain segments (TUR) with a specified location
  5. Hotel segments
  6. Passive hotel segments
  7. Other segments
  1. Departure time.

If the reordered itinerary contains any open-jaw trips, Smartpoint then creates an ARNK segment between the segments in the open-jaw trip.

  1. Recreating the previous stored fares by retrieving the pricing entries (*T).
  2. Updating the segment numbers in the price entries to reflect the current position of the segments in the PNR.
  3. Recreating the stored fares in the same order as they were before in the *LF section.
  4. Storing the rebooked fare.
  5. If the rebooked segment did not have any previous stored fare related, the new stored fare is added after the existing stored fares.
  6. If the rebooked segment had a previous stored fare related, the new stored fare created in the same position as the original stored fare.

Reordering and Re-Storing with Commands

There are three command options for reordering segments and/or re-storing stored fares.

Command

Description

#RO

Reorders the itinerary chronologically according to a precedence logic between segment types.

This command reorders the current itinerary based on:

  1. Departure time (standardized to UTC to handle multiple time zones in the itinerary).
  2. Precedence of segments based on type.

Segments are ordered based on the following rankings:

  1. Air segments
  2. Car rental segments
  3. Passive car segments
  4. Limousines and retain segments (TUR) with a specified location
  5. Hotel segments
  6. Passive hotel segments
  7. Other segments
  1. Departure time.

If the reordered itinerary contains any open-jaw trips, Smartpoint then creates an ARNK segment between the segments in the open-jaw trip.

#RS

Re-stores the stored fares.

Important! You can use this command when stored fares (ATFQ) are invalidated because segment positioning has changed.

Smartpoint recreates (re-stores) the current stored fares in the PNR by:

  1. Determining the relationship between stored fares and the existing segments in the PNR related to those stored fares.
  2. Retrieving the original pricing entry used to store the fare (*T).
  3. Reading the stored fare response to extract the price as booked ($B) from the ATFQ lines.
  4. Canceling the current stored fares in the PNR and using the price entries stored in the previous step to recreate them. The segment numbers in these price entries are updated with the actual new position of the air segment in the PNR.
  5. Displaying new price entries in the same order as the stored fare response in Step 2 to retain their position in the linear fare (*LF).
#RORS

Reorders the itinerary in the PNR and re-stores the stored fares (ATFQ).

#RORS is a combination of #RO and #RS. However, you can set the relationship between segments and stored fares using the Segments Association screen.

After you enter the #RORS command, a Segments Association pop-up screen is displayed.

In the Current Air Segments section:

  • If a segment still has its relationship with the stored fare, the ATFQ list displays with the correct stored fare.
  • If the segment no longer has a relationship to the stored fare, you can click the ATFQ arrow to select the desired stored fare.

The Association Preview section provides:

  • A summary of the existing stored fares.
  • The current assigned segment.
  • The original segment number for the stored fare (in parentheses).

Click Confirm Association to reorder the itinerary and re-store the fares in their new positions.

Known Issues

Re-order and re-store automatically adds ARNK segments when Smartpoint detects an open jaw trip in the itinerary. However, there are also several known issues in which additional ARNK segments may be created when an itinerary is reordered. ARNK segments that are not applicable to an open jaw trip can be deleted.